Thanks all for the quick action on the KEYS file

Steps:
* Reviewed list of changed JIRAs, all in YARN/MR.
* Release notes and CHANGES.txt looked good
* Verified checksums and signature via `gpg --verify`
* Ran `mvn apache-rat:check` on source tarball, passed
* Tarball size looks reasonable
* Built with "-Pdist" from source tarball
* Did some basic filesystem operations
* Ran a pi job, successfully returned a value of 4

Issues:
* Do we have a clean full test run?
* Maybe I'm using GPG wrong, but Sangjin's key isn't hooked into my web of
trust:

-> % gpg --verify hadoop-2.6.2-RC0-src.tar.gz.asc
hadoop-2.6.2-RC0-src.tar.gz
gpg: Signature made Wed 21 Oct 2015 09:16:07 PM PDT using RSA key ID
90348D47
gpg: Good signature from "Sangjin Lee <sj...@apache.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 8B44 A05C 3089 55D1 9195  6559 A5CE E20A 9034 8D47

Overall I'm +1 (binding), but it'd be good to see these two things
addressed. Maybe it's time for an SF key signing party.

Best,
Andrew

On Mon, Oct 26, 2015 at 2:35 PM, Li Lu <l...@hortonworks.com> wrote:

> Thanks Sangjin for the work! I downloaded the version, built it, and
> successfully ran a few jobs on my local machine in a single node setup. +1
> non-binding.
>
> Li Lu
>
> On Oct 26, 2015, at 14:08, Sangjin Lee <sj...@apache.org<mailto:
> sj...@apache.org>> wrote:
>
> Thanks Vinod! Thanks for the correction on the vote Andrew. Making some
> rookie mistakes here. :)
>
> On Mon, Oct 26, 2015 at 2:06 PM, Vinod Vavilapalli <
> vino...@hortonworks.com<mailto:vino...@hortonworks.com>>
> wrote:
>
> I was helping Sangjin offline with the release.
>
> We briefly discussed the KEYS problem before, but it missed my attention.
>
> I will get his KEYS committed right-away, the release is testable right
> away though.
>
> Regarding the voting period, let’s continue voting for two more days, the
> period also had the weekend during which a lot of people (atleast myself
> and team) didn’t pay attention to this vote.
>
> Thanks
> +Vinod
>
>
> On Oct 26, 2015, at 1:50 PM, Andrew Wang <andrew.w...@cloudera.com<mailto:
> andrew.w...@cloudera.com>>
> wrote:
>
> Hey Sangjin, did you add your release signing keys to the KEYS file? I
> don't see it here:
>
> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>
> Also only PMC votes are binding on releases, so I think we currently
> still
> stand at 0 binding +1s.
>
> On Mon, Oct 26, 2015 at 1:28 PM, Sangjin Lee <sjl...@gmail.com<mailto:
> sjl...@gmail.com>> wrote:
>
> That makes sense. Thanks for pointing that out. The git commit id is
> 0cfd050febe4a30b1ee1551dcc527589509fb681.
>
> On Mon, Oct 26, 2015 at 12:25 PM, Steve Loughran <
> ste...@hortonworks.com<mailto:ste...@hortonworks.com>>
> wrote:
>
>
> On 22 Oct 2015, at 22:14, Sangjin Lee <sj...@apache.org<mailto:
> sj...@apache.org>> wrote:
>
> Hi all,
>
> I have created a release candidate (RC0) for Hadoop 2.6.2.
>
> The RC is available at:
> http://people.apache.org/~sjlee/hadoop-2.6.2-RC0/
>
> The RC tag in git is: release-2.6.2-RC0
>
>
> Tags can move; we should *never* vote for a release of one.
>
> What is the git commit #  ?
>
> The list of JIRAs committed for 2.6.2:
>
>
>
>
> https://issues.apache.org/jira/browse/YARN-4101?jql=project%20in%20(HADOOP%2C%20HDFS%2C%20YARN%2C%20MAPREDUCE)%20AND%20fixVersion%20%3D%202.6.2
>
> The maven artifacts are staged at
>
>
> https://repository.apache.org/content/repositories/orgapachehadoop-1022/
>
> Please try out the release candidate and vote. The vote will run for 5
> days.
>
> Thanks,
> Sangjin
>
>
>
>
>
>
>

Reply via email to