Versions Compared

Old Version 3

changes.mady.by.user Jim Apple

Saved on

compared with

New Version 4

changes.mady.by.user Jim Apple

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This page describes the procedures that the release manager and voting PMC members take during release time.

Release Manager

Release managers are self-selected

  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 Add yourself to the Apache Web-of-Trust by meeting face-to-face with a person so they can sign your key.
    1. Upload your new 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
  4. Propose a release on the dev@ list. It should start with the string "\[DISCUSS]"
  5. Make a new branch off of master called "branch-x.y.z", where x.y.z is the version you want to release
  6. Cherry-pick commits from master to your branch that you want to include in the release
  7. Test it
  8. Make a tarball and add it to dev/ with SVN. Also add your signature, as well as md5 and sha1 checksums.
    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.
    2. 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.
    3. 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/
  9. Get informal feedback on your release candidate from the dev@ list. If you need to make changes, upload new release candidates - never overwrite old ones.
  10. 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 what each type of vote means
    4. Explain the conditions for the vote passing
    5. Include a link to this page
    6. Be consistent with the Impala bylaws. FOr instance, at the moment I am writing this wiki page, votes stay open for 72 hours.
  11. If the vote passes, and Impala has yet to graduate, take a vote in the incubator PMC, following current incubator policy.
  12. Publish the release.

PMC member

  1. Download the tarball. Check the signature and the checksums.
  2. Test it 
  3. Check compliance with ASF release policy.
  4. Vote

...