Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: mentors are on PPMC and IMPC

...

  1. Make a code signing key if you don't have one yet
    1. Publish your key if you haven't done so yet
  2. If you haven't done so yet, add yourself to the Apache Web-of-Trust by meeting face-to-face with a person so they can sign your key
    1. Publish your signed key
  3. If you haven't done so before, add your key to the KEYS file in the release staging area and the release distribution area
    1. The staging area is https://dist.apache.org/repos/dist/dev/incubator/impala/. Once graduated, it will presumably be https://dist.apache.org/repos/dist/dev/impala/
    2. The release area is https://dist.apache.org/repos/dist/release/incubator/impala/, and will presumably be https://dist.apache.org/repos/dist/release/impala/ after graduation.
  4. Pick a commit in the "master" branch you want to release from and test it.
  5. Test the licencing using Apache RAT; follow the instructions in bin/check-rat-report.py.
  6. Propose a release on the dev@ list. It should start with the string "[DISCUSS]". Explain that this is not a "[VOTE]", and that anyone may participate.
  7. Make a new branch off of your commit called "branch-x.y.z", where x.y.z is the version you want to release
    1. In this branch (but not in master) update the version number in bin/save-version.sh to x.y.z-RELEASE
  8. Continue testing. If you find bugs, file them. When they are fixed, cherry-pick the fixes from master to your branch that you want to include in the release
    1. Code Block
      languagebash
      git fetch apache # to make sure you have the latest master
      git log apache/master # to find the commits you want to cherry-pick
      git checkout apache/branch-x.y.z
      git checkout -b x.y.z-patch-foo # the name doesn't matter - it will only be in your local workstation
      git cherry-pick b4d1a3... # or whatever git hashes
      # then resolve conflicts, if there are any
      # cherry-pick some more commits:
      git cherry-pick ....
      git cherry-pick .....
      git push apache HEAD:branch-x.y.z
    2. At that time, tag the tree at the release candidate

      Code Block
      languagebash
      git fetch apache
      git checkout apache/branch-x.y.z
      git tag -a x.y.z-rcw # when making release candidate w of version x.y.z
      git push apache x.y.z-rcw
  9. Make a release tarball:
    1. Make the tarball using git archive. Name it apache-impala-incubating-x.y.z.tar.gz, or apache-impala-x.y.z.tar.gz if Impala has graduated from the incubator.

      Code Block
      languagebash
      git archive --prefix=apache-impala-incubating-x.y.z/ -o /tmp/apache-impala-incubating-x.y.z.tar.gz x.y.z-rcw
    2. Make signature, as well as md5 and sha1 checksums:

      Code Block
      languagebash
      # Make the signature:
      gpg -u YOUR_APACHE_USER_NAME@apache.org --armor --output apache-impala-incubating-x.y.z.tar.gz.asc --detach-sign apache-impala-incubating-x.y.z.tar.gz
       
      # Make sure it worked:
      gpg --verify apache-impala-incubating-x.y.z.tar.gz.asc
       
      # Make checksums:
      md5sum apache-impala-incubating-x.y.z.tar.gz > apache-impala-incubating-x.y.z.tar.gz.md5
      sha1sum apache-impala-incubating-x.y.z.tar.gz > apache-impala-incubating-x.y.z.tar.gz.sha
       
      # Make sure they worked:
      md5sum --check apache-impala-incubating-x.y.z.tar.gz.md5
      sha1sum --check apache-impala-incubating-x.y.z.tar.gz.sha
  10. Before uploading your release candidate, follow the procedure in the section below on how to vote on a release. Don't upload until you could vote +1.

  11. Get commitments from at least five PMC members to vote on the artifact in the time frame for the upcoming vote. While we are incubating, the list of PMC members is at http://incubator.apache.org/projects/impala.html. Once Impala graduates, that list will presumably be available at http://people.apache.org/committers-by-project.html#impala-pmc.
  12. Upload the artifacts. While incubating, the location is https://dist.apache.org/repos/dist/dev/incubator/impala/. Once graduated, it will presumably be https://dist.apache.org/repos/dist/dev/impala/. Upload all four artifacts. Do not overwrite old release candidates.

    Code Block
    languagebash
    svn checkout https://dist.apache.org/repos/dist/dev/incubator/impala/
    cd impala/
    # The directory layout is x.y.z/RCw, where w is the release candidate number - RC1 is the first candidate, RC2 the second, and so on.
    mkdir -p x.y.z/RCw
    cd x.y.z/RCw
    cp /tmp/apache-impala-incubating-x.y.z.tar.gz* ./
    svn add .
    svn commit --username=YOUR_APACHE_USER_NAME -m "Impala x.y.z release candidate w"
  13. Take a vote on dev@. Your vote email should:
    1. Have a subject that starts with "[VOTE]"
    2. Explain what the vote is about
    3. Explain how to find the artifacts for testing, and include the tag and git tree hash they correspond to
    4. Explain what each type of vote means
    5. Explain the conditions for the vote passing, including how long the vote will remain open for.
    6. Include a link to this wiki page so voters can read the instructions in it on how to test, verify, and vote. 
    7. Be consistent with the Impala bylaws. For instance, at the moment I am writing this wiki page, votes stay open for 72 hours (not counting weekends), and only PPMC members (and mentors) have binding votes.
  14. When the vote closes, tally up the votes (who votes what) in a thread with the same title as the vote thread, but with "[RESULT] " prepended. That email should include a list of every vote, ala:

    No Format
    nopaneltrue
    +1 (binding):
     
    Alice Bobopolis
    Carol Davestein
     
    -1 (non-binding):
     
    Emily Frankfurt
  15. If the vote passes, and Impala has yet to graduate, take a vote in the incubator PMC, following current incubator policy.
    1. Subscribe to general@incubator.apache.org by sending mail to general-subscribe@ and responding to the email it sends back.
    2. Send an email to that list including:
      1. A link to the archive of the proposal thread from the dev@impala mailing list, available either http://mail-archives.apache.org/mod_mbox/impala-dev/ or https://lists.apache.org/list.html?dev@impala.apache.org
      2. A link to the archive of the [RESULT] of the vote from the dev@impala mailing list.
      3. A link to the artifacts for testing
      4. A link to the KEYS file with the signatures
      5. A link to the git tag the release candidate tarball was created from
      6. The hash of the git commit the release candidate tarball was created from
      7. Instructions on using RAT on our code.
      8. Build instructions.
      9. A list of the IPMC members who have already +1ed. For instance, as of 28 September 2016, all of our mentors are IPMC members, so their +1s are good for either vote - the one with the PPMC or the one with the IPMC.
      10. No Format
        nopaneltrue
        This vote will be open for at least 72 hours, or until the necessary
        number of votes (3 +1) is reached.
        
        [ ] +1 Approve the release
        [ ] -1 Don't approve the release (please provide specific comments)
  16. Once that vote passes, tag the git tree at the release:

    Code Block
    languagebash
    git fetch apache
    git checkout apache/branch-x.y.z
    git tag -a x.y.z
    git push apache x.y.z
  17. Publish the release. While incubating, the location is https://dist.apache.org/repos/dist/release/incubator/impala/. Once graduated, it will presumably be https://dist.apache.org/repos/dist/release/impala/. Upload all four artifacts.

    Code Block
    languagebash
    svn checkout https://dist.apache.org/repos/dist/release/incubator/impala/
    cd impala/
    mkdir x.y.z
    cd x.y.z
    cp /tmp/apache-impala-incubating-x.y.z.tar.gz* ./
    svn add .
    svn commit --username=YOUR_APACHE_USER_NAME
    # You will be prompted to write a commit message. Make it look like (without the '#'s):
    #
    # Impala release x.y.z
    # 
    # PPMC vote thread: ...
    #
    # PPMC vote results thread: ...
    #
    # IPMC vote thread: ...
    #
    # IMPC vote results thread: ...
  18. Wait 24 hours for mirrors to catch up.
  19. Announce the release to dev@, user@, and update the downloads.html page (on the asf-site branch of the git repo) to point to the latest downloads.
  20. Send a patch review to the master branch to update its version number to "p.q.r-SNAPSHOT" (where p.q.r is greater than x.y.z)

...