I'm in the process of testing this. One nit that I think we should fix: apache-impala-incubating-2.7.0-rc1.tar.gz unpacks to incubator-impala. I think we should stick with the normal convention of unpacking to a directory with the same name as the tarball (or maybe apache-impala-incubating-2.7.0).
On Wed, Sep 7, 2016 at 2:16 PM, Henry Robinson <[email protected]> wrote: > Jim, this is great work (by everyone) and the culmination of a ton of > effort. Thanks for getting us to this stage! > > On 7 September 2016 at 14:08, Jim Apple <[email protected]> wrote: > > > I have put a release candidate, along with checksums and a > > cryptographic signature, in > > > > https://dist.apache.org/repos/dist/dev/incubator/impala/2.7.0/ > > > > I will be calling for a vote from the PPMC soon. This thread is not > > the vote thread. > > > > That vote will only pass, according to our bylaws, if it has 3 binding > > +1 votes and more binding +1 votes than -1 votes. Only the votes of > > PPMC members are binding, but anyone may vote. > > > > If that vote passes, I will ask the Incubator PMC to approve the > > release candidate, following the rules on > > > > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > > > > To +1 a release candidate, you will need to verify it. This includes: > > > > 1. Verifying the signature. You can import my code-signing public key > > from gpg using the instructions in > > > > https://dist.apache.org/repos/dist/dev/incubator/impala/KEYS > > > > You can also find that key at > > > > https://pgp.mit.edu/pks/lookup?op=get&search=0x91EE43066850196C > > > > or > > > > http://home.apache.org/keys/committer/jbapple > > > > You will be able to verify the signature by typing > > > > gpg --verify apache-impala-incubating-2.7.0-rc1.tar.gz.asc > > apache-impala-incubating-2.7.0-rc1.tar.gz > > > > This should happen on a machine you are the sole administrator of and > > that you have physical control of: > > > > http://www.apache.org/dev/release.html#owned-controlled-hardware > > > > 2. Build and test. You can do the testing on another machine - for > > instance, you can upload the RC1 tree to a git repo and point your CI > > tool at that repo. > > > > 3. "verify[ing] that the package meets the requirements of the ASF > > policy on releases" > > > > I suppose that means http://www.apache.org/dev/release.html. I am > > asking for clarification on that from our incubating mentors. > > > > Thank you! > > > > > > -- > Henry Robinson > Software Engineer > Cloudera > 415-994-6679 >
