[VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread Konstantin Boudnik
All, I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would like to release. This is a stabilization release that includes fixed for a couple a of issues discovered in the testing with BigTop 0.6.0 release candidate. The RC is available at: http://people.apache.org/~cos/had

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread Sangjin Lee
+1 (non-binding) Thanks Cos. Sangjin On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a of > issues > dis

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread Alejandro Abdelnur
Verified MD5 & signature, built, configured pseudo cluster, run a couple of sample jobs, tested HTTPFS. Still, something seems odd. The HDFS CHANGES.txt has the following entry under 2.0.5-alpha: HDFS-4646. createNNProxyWithClientProtocol ignores configured timeout value (Jagane Sundar via cos

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread J. Rottinghuis
Thanks for the hadoop-2.0.5-alpha RC0 Cos! +1 (non-binding) in principle for a 2.0.5-alpha release. Similar to Alejandro I see that: /hadoop-2.0.5-alpha-src/hadoop-hdfs-project/README.txt (has 2.0.4 release date missing): Release 2.0.5-alpha - UNRELEASED Release 2.0.4-alpha - UNRELEASED /hadoop-

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread Konstantin Boudnik
Alejandro, thanks for looking into this. Indeed - I missed the 2.0.5-alpha section in YARN CHANGES.txt. Added now. As for HDFS-4646: apparently I didn't get into to branch-2.0.4-alpha back then, although I distinctively remember doing this. Let me pull it into 2.0.5-alpha and update CHANGES.txt to

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread Konstantin Boudnik
Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha and later. It has been committed as r1465124 The reason it isn't normally visible because of the weird commit message: svn merge -c1465121 from trunk So, we good. I am done with the CHANGES.txt fixed that

[VOTE] Release Apache Hadoop 2.0.5-alpha (rc1)

2013-05-31 Thread Konstantin Boudnik
All, I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would like to release. This is a stabilization release that includes fixed for a couple a of issues discovered in the testing with BigTop 0.6.0 release candidate. The RC is available at: http://people.apache.org/~cos/had

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-05-31 Thread J. Rottinghuis
Thanks for fixing Cos. http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/ looks good to me. +1 (non-binding) Thanks, Joep On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik wrote: > Ok, WRT HDFS-4646 - it is all legit and the code is in branch-2.0.4-alpha > and > later. It has been commit

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-01 Thread Alejandro Abdelnur
On RC1, verified MD5 & signature, built, configured pseudo cluster, run a couple of sample jobs, tested HTTPFS. CHANGES.txt files contents are correct now. Still, a minor NIT, they have 2.0.5 as UNRELEASED, shouldn't they have a date (I would assume the date the vote ends). Thanks On Fri, May 3

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-01 Thread Roman Shaposhnik
On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would > like to release. > > This is a stabilization release that includes fixed for a couple a of issues > discovered in the testing with BigTop 0.6.0 relea

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Konstantin Boudnik
Alejandro, I believe this is chicken and egg problem: I can't put release date into unreleased tarball. Looking into 2.0.4-alpha source tarball I see the same situation: Release 2.0.4-alpha - UNRELEASED But in the trunk and branch-2 the release data is in place. I don't think this is an issue. B

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Alejandro Abdelnur
I know we had this issue before. But and easy way to solve it it would be using as release date the date the vote ends. Anyway, not a big deal if we are not cutting a new rc for other reason +1 on rc1 Thx On Jun 2, 2013, at 12:04 AM, Konstantin Boudnik wrote: > Alejandro, > > I believe this

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Konstantin Boudnik
This is my first Hadoop release, so I am all ears ;) I looked at how Arun was cutting the previous 2.0.x and followed the example. Thanks for your input and help Alejandro! Regards, Cos On Sun, Jun 02, 2013 at 09:01AM, Alejandro Abdelnur wrote: > I know we had this issue before. But and easy

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Arun C Murthy
I record the 'release date' as the one on which the build is created. Not sure what Matt actually does on branch-1. Matt? hth, Arun On Jun 2, 2013, at 12:33 PM, Konstantin Boudnik wrote: > This is my first Hadoop release, so I am all ears ;) I looked at how Arun was > cutting the previous 2.0.x

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Konstantin Boudnik
On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote: > I record the 'release date' as the one on which the build is created. Not > sure what Matt actually does on branch-1. Matt? Arun, but you do this not in the release source tarball, right? Just in the rest of integration branches, ie branch-2

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Arun C Murthy
I do it in the release branch, so the release source tarball has the date. Arun On Jun 2, 2013, at 6:41 PM, Konstantin Boudnik wrote: > On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote: >> I record the 'release date' as the one on which the build is created. Not >> sure what Matt actually do

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-02 Thread Konstantin Boudnik
On Sun, Jun 02, 2013 at 09:17PM, Arun C Murthy wrote: > I do it in the release branch, so the release source tarball has the date. I guess 2.0.4-alpha was cut differently for whatever reason, 'cause i see the UNRELEASED date in the source tarball. As I said - if anyone feels strongly about it I w

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

2013-06-03 Thread Konstantin Boudnik
Ok, if this the consensus on the issue, then tonight I will cut rc2 with only CHANGES.txt release dates update. After that I will extend the vote once again. Sorry for the hassle to all who did voted before. Cos On Mon, Jun 03, 2013 at 12:18AM, Doug Cutting wrote: > On Sun, Jun 2, 2013 at 9:01

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc1)

2013-05-31 Thread J. Rottinghuis
+1 (non-binding) Joep On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a of > issues > discovered in the t

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc1)

2013-06-02 Thread Konstantin Shvachko
+1 Did basic verification and testing. Thanks, --Konst On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I > would > like to release. > > This is a stabilization release that includes fixed for a couple a

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc1)

2013-06-03 Thread Roman Shaposhnik
NOTE: for consistency I'm moving my vote to the RC1 thread. On Fri, May 31, 2013 at 9:27 PM, Konstantin Boudnik wrote: > All, > > I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would > like to release. > > This is a stabilization release that includes fixed for a couple a

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Konstantin Boudnik
I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. The difference between rc1 and rc2 is the "optimistic release date" is set for 06/06/2013 in the CHANGES.txt files. The binary artifact is the same - there's no need to rebuild it. The maven artifacts are the same. The difference

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Alejandro Abdelnur
+1 RC2. Verified MD5 & signature, checked CHANGES.txt files, built, configured pseudo cluster, run a couple of sample jobs, tested HTTPFS. On Mon, Jun 3, 2013 at 12:51 PM, Konstantin Boudnik wrote: > I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. > > The difference between rc

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Chris Douglas
+1 Checksum and signature match, ran some unit tests, checked diff against 2.0.4-alpha. Thanks for seeing this through, Cos. -C On Mon, Jun 3, 2013 at 1:13 PM, Alejandro Abdelnur wrote: > +1 RC2. Verified MD5 & signature, checked CHANGES.txt files, built, > configured pseudo cluster, run a coup

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Sandy Ryza
+1 (non-binding) Built from source, ran a few sample jobs on a pseudo-distributed cluster On Mon, Jun 3, 2013 at 3:22 PM, Chris Douglas wrote: > +1 > > Checksum and signature match, ran some unit tests, checked diff > against 2.0.4-alpha. > > Thanks for seeing this through, Cos. -C > > On Mon,

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Roman Shaposhnik
On Mon, Jun 3, 2013 at 12:51 PM, Konstantin Boudnik wrote: > I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. > > The difference between rc1 and rc2 is the "optimistic release date" is set for > 06/06/2013 in the CHANGES.txt files. > > The binary artifact is the same - there's no

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-03 Thread Konstantin Shvachko
+1 Thanks, --Konst On Mon, Jun 3, 2013 at 12:51 PM, Konstantin Boudnik wrote: > I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. > > The difference between rc1 and rc2 is the "optimistic release date" is set > for > 06/06/2013 in the CHANGES.txt files. > > The binary artifact

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-04 Thread Kihwal Lee
+1 Built from source and ran a couple of jobs in a pseudo-distributed cluster. Kihwal On 6/3/13 2:51 PM, "Konstantin Boudnik" wrote: >I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. > >The difference between rc1 and rc2 is the "optimistic release date" is >set for >06/06/2013

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-04 Thread Thomas Graves
Cos, The name of the mds file for the binary tar is missing a "." in your apache directory: hadoop-2.0.5-alphatar.gz.mds Contents of it are fine though so you might just add the ".". Also the NOTICE.txt, README.

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-04 Thread Konstantin Boudnik
Good point Thomas - I have just fixed the name of the file. Nice catch! Sigh... these three text files... If anyone feels strongly about having them in place - I will update the tarballs and recalculate the checksums. Or just leave it as is, perhaps? So, either way is fine with me. Thanks, Cos

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

2013-06-05 Thread Anatoli Fomenko
: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2) I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha. The difference between rc1 and rc2 is the "optimistic release date" is set for 06/06/2013 in the CHANGES.txt files. The binary artifact is the same - there's no need to