from:"Konstantin Boudnik"

Darn CHANGES - apparently they just hate me. I agree that needs to be
addressed. I will spin-up rc1 tonight and restart the vote.

Thanks,
  Cos

On Wed, Aug 14, 2013 at 10:40AM, Alejandro Abdelnur wrote:
 OK:
 * verified MD5
 * verified signature
 * expanded source tar and did a build
 * configured pseudo cluster and run a couple of example MR jobs
 * did a few HTTP calls to HTTFS
 
 NOT OK:
 * CHANGES.txt files have 2.0.6 as UNRELEASED, they should have the date the
 RC vote ends
 * 'mvn apache-rat:check' fails, releasenotes HTML files don't have license
 headers,
 
 I think we need to address the NO OK points (specially the last one), they
 are trivial.
 
 Thanks.
 
 
 
 On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik c...@apache.org wrote:
 
  All,
 
  I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I
  would
  like to release.
 
  This is a stabilization release that includes fixed for a couple a of
  issues
  as outlined on the security list.
 
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
  The RC tag in svn is here:
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc0
 
  The maven artifacts are available via repository.apache.org.
 
  Please try the release bits and vote; the vote will run for the usual 7
  days.
 
  Thanks for your voting
Cos
 
 
 
 
 -- 
 Alejandro

Re: [VOTE] Release Apache Hadoop 2.0.6-alpha

Alejandro,

looking into the source code: it seems that release notes never had license
boilerplate in it, hence 2.0.6-alpha doesn't have as well.

I have fixed CHANGES with new optimistic date of the release and upload rc1
right now.

Please let me know if you feel like we need start doing the license for the
releasenotes in this release.

Thanks,
  Cos

On Wed, Aug 14, 2013 at 10:40AM, Alejandro Abdelnur wrote:
 OK:
 * verified MD5
 * verified signature
 * expanded source tar and did a build
 * configured pseudo cluster and run a couple of example MR jobs
 * did a few HTTP calls to HTTFS
 
 NOT OK:
 * CHANGES.txt files have 2.0.6 as UNRELEASED, they should have the date the
 RC vote ends
 * 'mvn apache-rat:check' fails, releasenotes HTML files don't have license
 headers,
 
 I think we need to address the NO OK points (specially the last one), they
 are trivial.
 
 Thanks.
 
 
 
 On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik c...@apache.org wrote:
 
  All,
 
  I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I
  would
  like to release.
 
  This is a stabilization release that includes fixed for a couple a of
  issues
  as outlined on the security list.
 
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
  The RC tag in svn is here:
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc0
 
  The maven artifacts are available via repository.apache.org.
 
  Please try the release bits and vote; the vote will run for the usual 7
  days.
 
  Thanks for your voting
Cos
 
 
 
 
 -- 
 Alejandro


signature.asc
Description: Digital signature

Re: [VOTE] Release Apache Hadoop 2.0.6-alpha

Sure Alejandro, not a big deal - I agree. Uploaded RC1 and restartig the vote
right away. Thanks for catching this!

Cos

On Thu, Aug 15, 2013 at 09:08PM, Alejandro Abdelnur wrote:
 it should be straight forward adding the license headers to the release
 notes. please make sure apache-rat:check passes on the RC before publishing
 it.
 
 Arun, as you are about to cut the new RC for 2.1.0-beta, can you please
 make sure the license headers are used in the releasenotes HTML files?
 
 Thx
 
 
 On Thu, Aug 15, 2013 at 8:02 PM, Konstantin Boudnik c...@apache.org wrote:
 
  Alejandro,
 
  looking into the source code: it seems that release notes never had license
  boilerplate in it, hence 2.0.6-alpha doesn't have as well.
 
  I have fixed CHANGES with new optimistic date of the release and upload rc1
  right now.
 
  Please let me know if you feel like we need start doing the license for the
  releasenotes in this release.
 
  Thanks,
Cos
 
  On Wed, Aug 14, 2013 at 10:40AM, Alejandro Abdelnur wrote:
   OK:
   * verified MD5
   * verified signature
   * expanded source tar and did a build
   * configured pseudo cluster and run a couple of example MR jobs
   * did a few HTTP calls to HTTFS
  
   NOT OK:
   * CHANGES.txt files have 2.0.6 as UNRELEASED, they should have the date
  the
   RC vote ends
   * 'mvn apache-rat:check' fails, releasenotes HTML files don't have
  license
   headers,
  
   I think we need to address the NO OK points (specially the last one),
  they
   are trivial.
  
   Thanks.
  
  
  
   On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik c...@apache.org
  wrote:
  
All,
   
I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I
would
like to release.
   
This is a stabilization release that includes fixed for a couple a of
issues
as outlined on the security list.
   
The RC is available at:
http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
The RC tag in svn is here:
   
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc0
   
The maven artifacts are available via repository.apache.org.
   
Please try the release bits and vote; the vote will run for the usual 7
days.
   
Thanks for your voting
  Cos
   
   
  
  
   --
   Alejandro
 
 
 
 
 -- 
 Alejandro


signature.asc
Description: Digital signature

[VOTE] Release Apache Hadoop 2.0.6-alpha (RC1)

All,

I have created a release candidate (rc1) for hadoop-2.0.6-alpha that I would
like to release.

This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.

The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc1/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc1

The maven artifacts are available via repository.apache.org.

The only difference between rc0 and rc1 is ASL added to releasenotes.html and
updated release dates in CHANGES.txt files.

Please try the release bits and vote; the vote will run for the usual 7 days.

Thanks for your voting
  Cos



signature.asc
Description: Digital signature

[VOTE] Release Apache Hadoop 2.0.6-alpha

2013-08-10 Thread Konstantin Boudnik

All,

I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I would
like to release.

This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.

The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.6-alpha-rc0

The maven artifacts are available via repository.apache.org.

Please try the release bits and vote; the vote will run for the usual 7 days.

Thanks for your voting
  Cos



signature.asc
Description: Digital signature

Re: creating 2.2.0 version in JIRA

2013-07-05 Thread Konstantin Boudnik

Same here.

On Tue, Jul 02, 2013 at 03:54PM, Alejandro Abdelnur wrote:
 We need clarification on this then.
 
 I was under the impression that branch-2 would be 2.2.0.
 
 thx
 
 On Tue, Jul 2, 2013 at 2:38 PM, Jason Lowe jl...@yahoo-inc.com wrote:
 
  I thought Arun intends for 2.2.0 to be created off of branch-2.1.0-beta
  and not off of branch-2.  As I understand it, only critical blockers will
  be the delta between 2.1.0-beta and 2.2.0 and items checked into branch-2
  should be marked as  fixed in 2.3.0.
 
  Part of the confusion is that currently branch-2 builds as 2.2.0-SNAPSHOT,
  but I believe Arun intended it to be 2.3.0-SNAPSHOT.
 
  Jason
 
 
  On 06/21/2013 12:05 PM, Alejandro Abdelnur wrote:
 
  Thanks Suresh, didn't know that, will do.
 
 
  On Fri, Jun 21, 2013 at 9:48 AM, Suresh Srinivas sur...@hortonworks.com
  wrote:
 
   I have added in to HDFS, HADOOP, MAPREDUCE projects. Can someone add it
  for
  YARN?
 
 
  On Fri, Jun 21, 2013 at 9:35 AM, Alejandro Abdelnur t...@cloudera.com
 
  wrote:
  When Arun created branch-2.1-beta he stated:
 
   The expectation is that 2.2.0 will be limited to content in
 
  branch-2.1-beta
 
  and we stick to stabilizing it henceforth (I've deliberately not
 
  created
 
  2.2.0
 
  fix-version on jira yet).
 
  I working/committing some JIRAs that I'm putting in branch-2 (testcases
 
  and
 
  improvements) but I don't want to put them in branch-2.1-beta as they
  are
  not critical and I don't won't add unnecessary noise to the
 
  branch-2.1-beta
 
  release work.
 
  Currently branch-2 POMs have a version 2.2.0 and the CHANGES.txt files
  as
  well.
 
  But because we did not create a JIRA version I cannot close those JIRAs.
 
  Can we please create the JIRA versions? later we can rename them.
 
  Thx
 
 
  --
  Alejandro
 
 
 
  --
  http://hortonworks.com/**download/ http://hortonworks.com/download/
 
 
 
 
 
 
 
 -- 
 Alejandro

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

2013-06-06 Thread Konstantin Boudnik

I am clearly +1 (non-binding) on the release.

With 8 +1s (3 binding), no -1s or 0s the vote passes.

Thanks to all who verified the bits, I'll push them out shortly.

Thanks,
  Cos

On Mon, Jun 03, 2013 at 12:51PM, 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 need to rebuild it. The maven
 artifacts are the same.
 
 The difference between the two RCs:
 
 svn diff \
   
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc1/ \
   https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc2/
 
 New RC builds are uploaded to the web.
 The RC is available at: http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc2/
 The RC tag in svn is here: 
 http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc2
 
 I would like to extend the vote for another three days for it is such a minor
 change that doesn't affect anything but the recorded release date. Please
 cast your vote before 06/06/2013 5pm PDT.
 
 Thanks for your patience!
   Cos
 
 On Fri, May 31, 2013 at 09:27PM, 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 testing with BigTop 0.6.0 release candidate.
  
  The RC is available at: 
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
  The RC tag in svn is here: 
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc1
  
  The maven artifacts will be available via repository.apache.org on Sat, June
  1st, 2013 at 2 pm PDT as outlined here
  http://s.apache.org/WKD
  
  Please try the release bits and vote; the vote will run for the 3 days,
  because this is just a version name change. The bits are identical to the 
  ones
  voted on before in 
  http://s.apache.org/2041move
  
  Thanks for your voting
Cos

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

On Tue, Jun 04, 2013 at 08:47PM, Thomas Graves wrote:
 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
 http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc2/hadoop-2.0.5-alphatar
 .gz.mds
 
 Contents of it are fine though so you might just add the ..
 
 Also the NOTICE.txt, README.txt, and LICENSE.txt files are missing from
 the top level directory in both the src and binary tar ball.
 
 Everything else looks good. Verified checksums, signatures, built, ran
 single node cluster.
 
 Thanks,
 Tom
  
 
 
 On 6/3/13 2:51 PM, Konstantin Boudnik c...@apache.org 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 need to rebuild it. The maven
 artifacts are the same.
 
 The difference between the two RCs:
 
 svn diff \
   
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc
 1/ \
   
 https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc
 2/
 
 New RC builds are uploaded to the web.
 The RC is available at:
 http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc2/
 The RC tag in svn is here:
 http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc2
 
 I would like to extend the vote for another three days for it is such a
 minor
 change that doesn't affect anything but the recorded release date. Please
 cast your vote before 06/06/2013 5pm PDT.
 
 Thanks for your patience!
   Cos
 
 On Fri, May 31, 2013 at 09:27PM, 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 testing with BigTop 0.6.0 release candidate.
  
  The RC is available at:
 http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
  The RC tag in svn is here:
 http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc
 1
  
  The maven artifacts will be available via repository.apache.org on Sat,
 June
  1st, 2013 at 2 pm PDT as outlined here
  http://s.apache.org/WKD
  
  Please try the release bits and vote; the vote will run for the 3 days,
  because this is just a version name change. The bits are identical to
 the ones
  voted on before in
  http://s.apache.org/2041move
  
  Thanks for your voting
Cos

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 AM, Alejandro Abdelnur t...@cloudera.com wrote:
  [...] an easy way to solve it it would be using as release date the date 
  the vote ends.
 
 +1 This is what I've done for release candidate builds.
 
 Doug

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 between the two RCs:

svn diff \
  https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc1/ \
  https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc2/

New RC builds are uploaded to the web.
The RC is available at: http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc2/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc2

I would like to extend the vote for another three days for it is such a minor
change that doesn't affect anything but the recorded release date. Please
cast your vote before 06/06/2013 5pm PDT.

Thanks for your patience!
  Cos

On Fri, May 31, 2013 at 09:27PM, 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 testing with BigTop 0.6.0 release candidate.
 
 The RC is available at: http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
 The RC tag in svn is here: 
 http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc1
 
 The maven artifacts will be available via repository.apache.org on Sat, June
 1st, 2013 at 2 pm PDT as outlined here
 http://s.apache.org/WKD
 
 Please try the release bits and vote; the vote will run for the 3 days,
 because this is just a version name change. The bits are identical to the ones
 voted on before in 
 http://s.apache.org/2041move
 
 Thanks for your voting
   Cos
 


signature.asc
Description: Digital signature

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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. But I would be happy to fix it if this seems to be a problem.

Thanks,
Cos

On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
 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 31, 2013 at 9:39 PM, J. Rottinghuis jrottingh...@gmail.comwrote:
 
  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 c...@apache.org
  wrote:
 
   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 you guys have
  noted
   earlier and will be re-spinning RC1 in a few.
  
   Cos
  
   On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
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 reflect it.
   Also, I
will do JIRA in a moment.
   
Joep, appreciate the thorough examination. I have fixed the dates for
  the
releases 2.0.4-alpha. As for the top-level readme file - sorry I wasn't
   aware
about them. As for the binary: I am pretty sure we are only releasing
   source
code, but I will put binaries into the rc1 respin.
   
I will respin rc1 shortly. Appreciate the feedback!
  Cos
   
On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
 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)

 but I don't see that in the branch.

 And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it
   should
 be there empty).

 Cos, can you please look at these 2 things and explain/fix?

 Thanks.



 On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org
   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 release candidate.
 
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
  The RC tag in svn is here:
 
  
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
 
  The maven artifacts will be available via repository.apache.org on
   Sat,
  June
  1st, 2013 at 2 pm PDT as outlined here
  http://s.apache.org/WKD
 
  Please try the release bits and vote; the vote will run for the 3
   days,
  because this is just a version name change. The bits are identical
   to the
  ones
  voted on before in
  http://s.apache.org/2041move
 
  Thanks for your voting
Cos
 
 


 --
 Alejandro
  
  
  
 
 
 
 
 -- 
 Alejandro

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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 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 c...@apache.org wrote:
 
  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. But I would be happy to fix it if this seems to be a problem.
  
  Thanks,
  Cos
  
  On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
  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 31, 2013 at 9:39 PM, J. Rottinghuis 
  jrottingh...@gmail.comwrote:
  
  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 c...@apache.org
  wrote:
  
  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 you guys have
  noted
  earlier and will be re-spinning RC1 in a few.
  
  Cos
  
  On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
  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 reflect it.
  Also, I
  will do JIRA in a moment.
  
  Joep, appreciate the thorough examination. I have fixed the dates for
  the
  releases 2.0.4-alpha. As for the top-level readme file - sorry I wasn't
  aware
  about them. As for the binary: I am pretty sure we are only releasing
  source
  code, but I will put binaries into the rc1 respin.
  
  I will respin rc1 shortly. Appreciate the feedback!
   Cos
  
  On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
  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)
  
  but I don't see that in the branch.
  
  And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it
  should
  be there empty).
  
  Cos, can you please look at these 2 things and explain/fix?
  
  Thanks.
  
  
  
  On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org
  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 release candidate.
  
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
  The RC tag in svn is here:
  
  
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
  
  The maven artifacts will be available via repository.apache.org on
  Sat,
  June
  1st, 2013 at 2 pm PDT as outlined here
 http://s.apache.org/WKD
  
  Please try the release bits and vote; the vote will run for the 3
  days,
  because this is just a version name change. The bits are identical
  to the
  ones
  voted on before in
 http://s.apache.org/2041move
  
  Thanks for your voting
   Cos
  
  
  
  
  --
  Alejandro
  
  
  
  
  
  
  
  -- 
  Alejandro


signature.asc
Description: Digital signature

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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 and trunk. Am I correct?

Thanks,
  Cos

 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 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 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 c...@apache.org wrote:
  
  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. But I would be happy to fix it if this seems to be a problem.
  
  Thanks,
  Cos
  
  On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
  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 31, 2013 at 9:39 PM, J. Rottinghuis 
  jrottingh...@gmail.comwrote:
  
  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 c...@apache.org
  wrote:
  
  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 you guys have
  noted
  earlier and will be re-spinning RC1 in a few.
  
  Cos
  
  On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
  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 reflect it.
  Also, I
  will do JIRA in a moment.
  
  Joep, appreciate the thorough examination. I have fixed the dates for
  the
  releases 2.0.4-alpha. As for the top-level readme file - sorry I 
  wasn't
  aware
  about them. As for the binary: I am pretty sure we are only releasing
  source
  code, but I will put binaries into the rc1 respin.
  
  I will respin rc1 shortly. Appreciate the feedback!
  Cos
  
  On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
  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)
  
  but I don't see that in the branch.
  
  And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it
  should
  be there empty).
  
  Cos, can you please look at these 2 things and explain/fix?
  
  Thanks.
  
  
  
  On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org
  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 release candidate.
  
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
  The RC tag in svn is here:
  
  
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
  
  The maven artifacts will be available via repository.apache.org on
  Sat,
  June
  1st, 2013 at 2 pm PDT as outlined here
http://s.apache.org/WKD
  
  Please try the release bits and vote; the vote will run for the 3
  days,
  because this is just a version name change. The bits are identical
  to the
  ones
  voted on before in
http://s.apache.org/2041move
  
  Thanks for your voting
  Cos
  
  
  
  
  --
  Alejandro
  
  
  
  
  
  
  
  -- 
  Alejandro
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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 will alter the CHANGES.txt
files

thanks,
  Cos

 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 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 and trunk. Am I correct?
  
  Thanks,
   Cos
  
  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 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 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 c...@apache.org wrote:
  
  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. But I would be happy to fix it if this seems to be a 
  problem.
  
  Thanks,
  Cos
  
  On Sat, Jun 01, 2013 at 08:04PM, Alejandro Abdelnur wrote:
  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 31, 2013 at 9:39 PM, J. Rottinghuis 
  jrottingh...@gmail.comwrote:
  
  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 c...@apache.org
  wrote:
  
  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 you guys have
  noted
  earlier and will be re-spinning RC1 in a few.
  
  Cos
  
  On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
  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 reflect 
  it.
  Also, I
  will do JIRA in a moment.
  
  Joep, appreciate the thorough examination. I have fixed the dates 
  for
  the
  releases 2.0.4-alpha. As for the top-level readme file - sorry I 
  wasn't
  aware
  about them. As for the binary: I am pretty sure we are only 
  releasing
  source
  code, but I will put binaries into the rc1 respin.
  
  I will respin rc1 shortly. Appreciate the feedback!
  Cos
  
  On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
  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)
  
  but I don't see that in the branch.
  
  And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it
  should
  be there empty).
  
  Cos, can you please look at these 2 things and explain/fix?
  
  Thanks.
  
  
  
  On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik 
  c...@apache.org
  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 release candidate.
  
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
  The RC tag in svn is here:
  
  
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
  
  The maven artifacts will be available via repository.apache.org on
  Sat,
  June
  1st, 2013 at 2 pm PDT

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

2013-06-01 Thread Konstantin Boudnik

Chris,

with 2.0.5-alpha (rc1) out, would you please take a look at the release bits?
I assume the four-digit numbering scheme issue has been resolved now.

Regards,
  Cos

On Thu, May 30, 2013 at 06:18PM, Chris Douglas wrote:
 On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik c...@apache.org wrote:
  I have no issues of changing the version to 2.0.5-alpha and restarting to 
  vote
  for the release content, e.g. 2 bug fixes. Shall I call 3 days re-vote 
  because
  of the number change?
 
 +1 Sounds great.
 
  Does the result of bylaw vote nullifies the unfinished vote started by Arun?
  Sorry, I am dense, apparently.
 
 Yes, nobody should feel bound by either vote. The bylaw change
 clarifies that release plans are for RMs to solicit feedback and gauge
 PMC support for an artifact, not pre-approvals for doing work.
 
  Can we limit the vote thread to the merits of the release then?
 
 Happily.
 
  That sound like adding an insult to injury, if my forth-language skills do 
  not
  mislead me.
 
 They do mislead you, or I've expressed the point imprecisely. We can
 take this offline. -C
 
On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote:
On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy 
a...@hortonworks.com wrote:
 Why not include MAPREDUCE-4211 as well rather than create one 
 release per patch?
   
From Cos's description, it sounded like these were backports of fixes
to help Sqoop2 and fix some build issues. If it's not just to fixup
leftover bugs in 2.0.4 *once* so downstream projects can integrate
against 2.0.4.1, and this a release series, then I've completely
misunderstood the purpose.
   
Cos, are you planning 2.0.4.2?
   
 Also, this is the first time we are seeing a four-numbered scheme 
 in Hadoop. Why not call this 2.0.5-alpha?
   
Good point. Since it contains only backports from branch-2, it would
make sense for it to be an intermediate release.
   
I shouldn't have to say this, but I'm changing my vote to -1 while we
work this out. -C
   
 On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:

 All,

 I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
 The RC tag in svn is here: 
 http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0

 The maven artifacts are available via repository.apache.org.

 Please try the release bits and vote; the vote will run for the 
 usual 7 days.

 Thanks for your voting
  Cos





signature.asc
Description: Digital signature

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

2013-06-01 Thread Konstantin Boudnik

I changes are completed, I have updated branch-2 and trunk CHANGES.txt files
as planned. Version of the branch-2 is set to 2.1.0-beta; 2.0.5-alpha release
artifacts are deployed to the staging area.

Thanks for your patience, guys!
  Cos

On Fri, May 31, 2013 at 12:45PM, Konstantin Boudnik wrote:
 Guys,
 
 I will be performing some changes wrt to moving 2.0.4.1 release candidate to
 2.0.5 space. As outline below by Alejandro:
 
 1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha
 that contains 2.0.4.1 changes
 2. consequently, set the artifacts version on the new branch to be 2.0.5-alpha
 3. the CHANGES.txt will be updated accordingly on the new 2.0.5 branch
 4. At this point I can cut an RC and put it out for re-vote. The staging can
 be done after the next two steps.
 
 I will be doing all these modifications in the next hour or so.
 
 Tomorrow at 1 pm PDT I would like to:
 1. update the version of the artifacts on branch-2 to become 2.1.0-SNAPSHOT
 2. update the CHANGES.txt in the trunk and branch-2 to reflect new version 
 names
 3. at this point it should safe to do the staging for 2.0.5-alpha RC
 
 To avoid any collisions during the last two steps - especially 2. - I would
 ask everyone to hold off the modifications of the CHANGES.txt files on trunk
 and branch-2 between 1 pm and 2 pm PDT.
 
 Please let me know if you see any flaw above, questions.
   Cos
 
  As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
  housekeeping as you work the new RC.
  
  * rename the svn branch
  * update the versions in the POMs
  * update the CHANGES.txt in trunk, branch-2 and the release branch
  * change the current 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
  version, change the fix version of the 2 JIRAs that make the RC
 
  I renamed 2.0.5-beta to 2.1.0-beta and 2.0.4.1-alpha to 2.0.5-alpha versions
  in jira for HADOOP, HDFS, YARN  MAPREDUCE.
 
  Please take care of the rest.
 
  Also, in branch-2, the version should be 2.1.0-SNAPSHOT.


signature.asc
Description: Digital signature

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

Thanks for the headstart Arun!

I will be sending a separate email to the *-dev@ lists outlining the plan and
the schedule of the changes, so we won't step on each other feet, like Vinod
expressed earlier.

Cos

On Fri, May 31, 2013 at 11:20AM, Arun C Murthy wrote:
 
 On May 30, 2013, at 8:41 PM, Alejandro Abdelnur wrote:
 
  Konstantin, Cos,
  
  As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
  housekeeping as you work the new RC.
  
  * rename the svn branch
  * update the versions in the POMs
  * update the CHANGES.txt in trunk, branch-2 and the release branch
  * change the current 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
  version, change the fix version of the 2 JIRAs that make the RC
 
 I renamed 2.0.5-beta to 2.1.0-beta and 2.0.4.1-alpha to 2.0.5-alpha versions
 in jira for HADOOP, HDFS, YARN  MAPREDUCE.
 
 Please take care of the rest.
 
 Also, in branch-2, the version should be 2.1.0-SNAPSHOT.
 
 thanks,
 Arun
 
  
  Thanks.
  
  
  On Thu, May 30, 2013 at 6:18 PM, Chris Douglas cdoug...@apache.org wrote:
  
  On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik c...@apache.org
  wrote:
  I have no issues of changing the version to 2.0.5-alpha and restarting
  to vote
  for the release content, e.g. 2 bug fixes. Shall I call 3 days re-vote
  because
  of the number change?
  
  +1 Sounds great.
  
  Does the result of bylaw vote nullifies the unfinished vote started by
  Arun?
  Sorry, I am dense, apparently.
  
  Yes, nobody should feel bound by either vote. The bylaw change
  clarifies that release plans are for RMs to solicit feedback and gauge
  PMC support for an artifact, not pre-approvals for doing work.
  
  Can we limit the vote thread to the merits of the release then?
  
  Happily.
  
  That sound like adding an insult to injury, if my forth-language skills
  do not
  mislead me.
  
  They do mislead you, or I've expressed the point imprecisely. We can
  take this offline. -C
  
  On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote:
  On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy 
  a...@hortonworks.com wrote:
  Why not include MAPREDUCE-4211 as well rather than create one
  release per patch?
  
  From Cos's description, it sounded like these were backports of
  fixes
  to help Sqoop2 and fix some build issues. If it's not just to
  fixup
  leftover bugs in 2.0.4 *once* so downstream projects can integrate
  against 2.0.4.1, and this a release series, then I've completely
  misunderstood the purpose.
  
  Cos, are you planning 2.0.4.2?
  
  Also, this is the first time we are seeing a four-numbered
  scheme in Hadoop. Why not call this 2.0.5-alpha?
  
  Good point. Since it contains only backports from branch-2, it
  would
  make sense for it to be an intermediate release.
  
  I shouldn't have to say this, but I'm changing my vote to -1
  while we
  work this out. -C
  
  On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:
  
  All,
  
  I have created a release candidate (rc0) for
  hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
  The RC tag in svn is here:
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0
  
  The maven artifacts are available via repository.apache.org.
  
  Please try the release bits and vote; the vote will run for
  the usual 7 days.
  
  Thanks for your voting
  Cos
  
  
  
  
  
  
  
  -- 
  Alejandro
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/

Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

Guys,

I will be performing some changes wrt to moving 2.0.4.1 release candidate to
2.0.5 space. As outline below by Alejandro:

1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha
that contains 2.0.4.1 changes
2. consequently, set the artifacts version on the new branch to be 2.0.5-alpha
3. the CHANGES.txt will be updated accordingly on the new 2.0.5 branch
4. At this point I can cut an RC and put it out for re-vote. The staging can
be done after the next two steps.

I will be doing all these modifications in the next hour or so.

Tomorrow at 1 pm PDT I would like to:
1. update the version of the artifacts on branch-2 to become 2.1.0-SNAPSHOT
2. update the CHANGES.txt in the trunk and branch-2 to reflect new version names
3. at this point it should safe to do the staging for 2.0.5-alpha RC

To avoid any collisions during the last two steps - especially 2. - I would
ask everyone to hold off the modifications of the CHANGES.txt files on trunk
and branch-2 between 1 pm and 2 pm PDT.

Please let me know if you see any flaw above, questions.
  Cos

 As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
 housekeeping as you work the new RC.
 
 * rename the svn branch
 * update the versions in the POMs
 * update the CHANGES.txt in trunk, branch-2 and the release branch
 * change the current 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
 version, change the fix version of the 2 JIRAs that make the RC

 I renamed 2.0.5-beta to 2.1.0-beta and 2.0.4.1-alpha to 2.0.5-alpha versions
 in jira for HADOOP, HDFS, YARN  MAPREDUCE.

 Please take care of the rest.

 Also, in branch-2, the version should be 2.1.0-SNAPSHOT.

Re: Heads up: moving from 2.0.4.1-alpha to 2.0.5-alpha

Indeed! The second part is happening on Saturday, JUN01 2013 1PM-2PM PST. 

On Fri, May 31, 2013 at 01:01PM, Alejandro Abdelnur wrote:
 Cos, just to be clear, this is happening SAT JUN01 1PM-2PM PST, not now
 (FRI MAY31 1PM PST). Correct?
 
 Thx
 
 On Fri, May 31, 2013 at 12:45 PM, Konstantin Boudnik c...@apache.org wrote:
 
  Guys,
 
  I will be performing some changes wrt to moving 2.0.4.1 release candidate
  to
  2.0.5 space. As outline below by Alejandro:
 
  1. I will create new 2.0.5-alpha branch from the current head of
  2.0.4-alpha
  that contains 2.0.4.1 changes
  2. consequently, set the artifacts version on the new branch to be
  2.0.5-alpha
  3. the CHANGES.txt will be updated accordingly on the new 2.0.5 branch
  4. At this point I can cut an RC and put it out for re-vote. The staging
  can
  be done after the next two steps.
 
  I will be doing all these modifications in the next hour or so.
 
  Tomorrow at 1 pm PDT I would like to:
  1. update the version of the artifacts on branch-2 to become 2.1.0-SNAPSHOT
  2. update the CHANGES.txt in the trunk and branch-2 to reflect new version
  names
  3. at this point it should safe to do the staging for 2.0.5-alpha RC
 
  To avoid any collisions during the last two steps - especially 2. - I would
  ask everyone to hold off the modifications of the CHANGES.txt files on
  trunk
  and branch-2 between 1 pm and 2 pm PDT.
 
  Please let me know if you see any flaw above, questions.
Cos
 
   As we change from 2.0.4.1 to 2.0.5 you'll need to do the following
   housekeeping as you work the new RC.
  
   * rename the svn branch
   * update the versions in the POMs
   * update the CHANGES.txt in trunk, branch-2 and the release branch
   * change the current 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
   version, change the fix version of the 2 JIRAs that make the RC
 
   I renamed 2.0.5-beta to 2.1.0-beta and 2.0.4.1-alpha to 2.0.5-alpha
  versions
   in jira for HADOOP, HDFS, YARN  MAPREDUCE.
 
   Please take care of the rest.
 
   Also, in branch-2, the version should be 2.1.0-SNAPSHOT.
 
 
 
 
 -- 
 Alejandro

[VOTE] Release Apache Hadoop 2.0.5-alpha

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/hadoop-2.0.5-alpha-rc0/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0

The maven artifacts will be available via repository.apache.org on Sat, June
1st, 2013 at 2 pm PDT as outlined here
http://s.apache.org/WKD

Please try the release bits and vote; the vote will run for the 3 days,
because this is just a version name change. The bits are identical to the ones
voted on before in 
http://s.apache.org/2041move

Thanks for your voting
  Cos

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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 reflect it. Also, I
will do JIRA in a moment.

Joep, appreciate the thorough examination. I have fixed the dates for the
releases 2.0.4-alpha. As for the top-level readme file - sorry I wasn't aware
about them. As for the binary: I am pretty sure we are only releasing source
code, but I will put binaries into the rc1 respin.

I will respin rc1 shortly. Appreciate the feedback!
  Cos

On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
 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)
 
 but I don't see that in the branch.
 
 And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it should
 be there empty).
 
 Cos, can you please look at these 2 things and explain/fix?
 
 Thanks.
 
 
 
 On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org 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 release candidate.
 
  The RC is available at:
  http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
  The RC tag in svn is here:
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
 
  The maven artifacts will be available via repository.apache.org on Sat,
  June
  1st, 2013 at 2 pm PDT as outlined here
  http://s.apache.org/WKD
 
  Please try the release bits and vote; the vote will run for the 3 days,
  because this is just a version name change. The bits are identical to the
  ones
  voted on before in
  http://s.apache.org/2041move
 
  Thanks for your voting
Cos
 
 
 
 
 -- 
 Alejandro


signature.asc
Description: Digital signature

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha

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 you guys have noted
earlier and will be re-spinning RC1 in a few.

Cos

On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
 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 reflect it. Also, I
 will do JIRA in a moment.
 
 Joep, appreciate the thorough examination. I have fixed the dates for the
 releases 2.0.4-alpha. As for the top-level readme file - sorry I wasn't aware
 about them. As for the binary: I am pretty sure we are only releasing source
 code, but I will put binaries into the rc1 respin.
 
 I will respin rc1 shortly. Appreciate the feedback!
   Cos
 
 On Fri, May 31, 2013 at 05:27PM, Alejandro Abdelnur wrote:
  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)
  
  but I don't see that in the branch.
  
  And, the YARN CHANGES.txt does not have the 2.0.5-alpha section (it should
  be there empty).
  
  Cos, can you please look at these 2 things and explain/fix?
  
  Thanks.
  
  
  
  On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik c...@apache.org 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 release candidate.
  
   The RC is available at:
   http://people.apache.org/~cos/hadoop-2.0.5-alpha-rc0/
   The RC tag in svn is here:
   http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc0
  
   The maven artifacts will be available via repository.apache.org on Sat,
   June
   1st, 2013 at 2 pm PDT as outlined here
   http://s.apache.org/WKD
  
   Please try the release bits and vote; the vote will run for the 3 days,
   because this is just a version name change. The bits are identical to the
   ones
   voted on before in
   http://s.apache.org/2041move
  
   Thanks for your voting
 Cos
  
  
  
  
  -- 
  Alejandro




signature.asc
Description: Digital signature

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

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/hadoop-2.0.5-alpha-rc1/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.5-alpha-rc1

The maven artifacts will be available via repository.apache.org on Sat, June
1st, 2013 at 2 pm PDT as outlined here
http://s.apache.org/WKD

Please try the release bits and vote; the vote will run for the 3 days,
because this is just a version name change. The bits are identical to the ones
voted on before in 
http://s.apache.org/2041move

Thanks for your voting
  Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 10:57AM, Arun C Murthy wrote:
I see you just re-opened MAPREUDCE-5211.

Why not include MAPREDUCE-5211 as well rather than create one release per
patch?

Arun, it is unclear if MAPREDUCE-5211 has implications in 2.0.4 as per
https://issues.apache.org/jira/browse/MAPREDUCE-5211?focusedCommentId=13670574page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13670574

Hence, there's a good chance that it never will be backported. And I don't
have any plans to created 'a release per patch'.

Also, this is the first time we are seeing a four-numbered scheme in Hadoop.
Why not call this 2.0.5-alpha?

There were precedents in four-numbered schemes before: 0.20.20[3-5].0 comes to
mind.

As for 2.0.5-alpha: The release numbering games and votes that had happened in
the last few weeks are very confusing. Some of them never been concluded, the
branches are moved and artifact versions seem to be colliding. 2.0.4.x seems
to work well for the stabilization purposes and it will allow to unblock
downstream and integration projects quickly.

Cos

Arun

On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:

All,

I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
The RC tag in svn is here:
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0

The maven artifacts are available via repository.apache.org.

Please try the release bits and vote; the vote will run for the usual 7
days.

Thanks for your voting
Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

There's no misunderstanding Chris - this release is to unblock downstream.

As for your question: I don't have a crystal ball; I wish though. I think the
answer depends on will be there more blocking bugs found in the later releases
of Bigtop or other downstream components.
This is bugfix release and, I guess, if there are more bugs found in the
future - more releases would have to be cut. Isn't this is why the software is
being released?

Now, the -1: I am not clear about the justification. What exactly we expect to
work out?

Cos

On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote:
 On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com wrote:
  Why not include MAPREDUCE-4211 as well rather than create one release per 
  patch?
 
 From Cos's description, it sounded like these were backports of fixes
 to help Sqoop2 and fix some build issues. If it's not just to fixup
 leftover bugs in 2.0.4 *once* so downstream projects can integrate
 against 2.0.4.1, and this a release series, then I've completely
 misunderstood the purpose.
 
 Cos, are you planning 2.0.4.2?
 
  Also, this is the first time we are seeing a four-numbered scheme in 
  Hadoop. Why not call this 2.0.5-alpha?
 
 Good point. Since it contains only backports from branch-2, it would
 make sense for it to be an intermediate release.
 
 I shouldn't have to say this, but I'm changing my vote to -1 while we
 work this out. -C
 
  On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:
 
  All,
 
  I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
  The RC tag in svn is here: 
  http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0
 
  The maven artifacts are available via repository.apache.org.
 
  Please try the release bits and vote; the vote will run for the usual 7 
  days.
 
  Thanks for your voting
   Cos

Re: Cannot update PoweredBy wiki page

Someone with proper karma needs to add you into ACL for this page.

On Thu, May 30, 2013 at 11:14PM, Adam Kawa wrote:
 Hi,
 
 When uploading new content (and information about my company), I got the
 exception
 Sorry, can not save page because rubbelloselotto.de is not allowed in
 this wiki.
 
 How could I solve it?
 
 Kind regards,
 Adam

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 03:18PM, Chris Douglas wrote:
 On Thu, May 30, 2013 at 2:39 PM, Konstantin Boudnik c...@apache.org wrote:
  There's no misunderstanding Chris - this release is to unblock downstream.
 
  As for your question: I don't have a crystal ball; I wish though. I think 
  the
  answer depends on will be there more blocking bugs found in the later 
  releases
  of Bigtop or other downstream components.
  This is bugfix release and, I guess, if there are more bugs found in the
  future - more releases would have to be cut. Isn't this is why the software 
  is
  being released?
 
 Sure, but they're all backports from the release currently marked for
 2.0.5. Either (a) these are really blocker bugs and we should roll a
 patch release or (b) some bleeding-edge work needs to work around this
 while branch-2 is released in the next few weeks. If it's not severe
 enough to justify disrupting the versioning of snapshot maven
 artifacts in branch-2, then we're clearly not in case (a).
 
 I thought this was the result of extensive testing, and 2.0.4.1 was a
 release to enable additional integration before 2.0.5. If we plan to
 roll more releases as a subset of the bug fixes committed to branch-2
 then just call it 2.0.5. Please make sure it- and any future,
 intermediate release- is worth the disruption.

There's no plans to release anything else at this point - this is a bug-fix
release, as I pointed out on a numerous occasions. There's no new features -
just 2 fixes.

2.0.5 matter became and still is too controversial at some point. The vote
started by Arun to override the results of the Konstantin's vote never been
closed. The downstream projects are handing in the middle of the air because
of that confusion. 

  Now, the -1: I am not clear about the justification. What exactly we expect 
  to
  work out?
 
 It's become fashionable to close threads and count votes in the middle
 of the discussion. I changed my vote instead of trusting you. -C

Have I missed something or you just called me a cheater and a lair right to my 
face?

Cos

  On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote:
  On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com 
  wrote:
   Why not include MAPREDUCE-4211 as well rather than create one release 
   per patch?
 
  From Cos's description, it sounded like these were backports of fixes
  to help Sqoop2 and fix some build issues. If it's not just to fixup
  leftover bugs in 2.0.4 *once* so downstream projects can integrate
  against 2.0.4.1, and this a release series, then I've completely
  misunderstood the purpose.
 
  Cos, are you planning 2.0.4.2?
 
   Also, this is the first time we are seeing a four-numbered scheme in 
   Hadoop. Why not call this 2.0.5-alpha?
 
  Good point. Since it contains only backports from branch-2, it would
  make sense for it to be an intermediate release.
 
  I shouldn't have to say this, but I'm changing my vote to -1 while we
  work this out. -C
 
   On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:
  
   All,
  
   I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
   The RC tag in svn is here: 
   http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0
  
   The maven artifacts are available via repository.apache.org.
  
   Please try the release bits and vote; the vote will run for the usual 7 
   days.
  
   Thanks for your voting
Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 03:11PM, Matt Foley wrote:
Hi Cos,
I would also request that you renumber the release candidate to just
three-numbers, hence 2.0.5-alpha.

Arun, are you willing to start the 2.1.x name-space for your next release,
so that 2.0.x-alpha can become an intermediate stabilization branch as Cos
and Konst want?

Let's get the facts straight, Matt, please: this want has been expressed in
the official vote here http://s.apache.org/ZMf Apparently, 2.0.5-alpha is
blocked now because of the another vote that hasn't been closed yet for
whatever reason. In order to unblock a number of releases in downstream
component I have moved forward with this release. Do you have any material
objections to the release that pursue this goal?

I just think that using four-number schemes was symptomatic of the
near-forking we had back in the 0.20.xxx.y days, and I really don't want to
go back there. Especially since you could say that 0.20.xxx.y is just
three significant numbers, the leading zero being inconsequential.

I dare to remind that forth part of the version is reserved - not in a
parallel universe, of course - for patch level aka bug fixes. It hardly can
be taken a sign of 'forking' by any definition.

Cos

So, would you please consider using 2.0.5-alpha?

As for the 2.0.5-SNAPSHOT in the branch-2 versioning, that's standard
usage. Whoever makes the 2.0.5 release (or any next release) is expected
to update the parent branch's SNAPSHOT default versioning, per
HowToReleasePostMavenization#Branchinghttps://wiki.apache.org/hadoop/HowToReleasePostMavenization#Branching,
step 6.

Thanks,
--Matt

On Thu, May 30, 2013 at 11:52 AM, Konstantin Boudnik c...@apache.org wrote:

On Thu, May 30, 2013 at 10:57AM, Arun C Murthy wrote:
I see you just re-opened MAPREUDCE-5211.

Why not include MAPREDUCE-5211 as well rather than create one release
per patch?

Arun, it is unclear if MAPREDUCE-5211 has implications in 2.0.4 as per

https://issues.apache.org/jira/browse/MAPREDUCE-5211?focusedCommentId=13670574page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13670574

Hence, there's a good chance that it never will be backported. And I don't
have any plans to created 'a release per patch'.

Also, this is the first time we are seeing a four-numbered scheme in
Hadoop.
Why not call this 2.0.5-alpha?

There were precedents in four-numbered schemes before: 0.20.20[3-5].0
comes to
mind.

As for 2.0.5-alpha: The release numbering games and votes that had
happened in
the last few weeks are very confusing. Some of them never been concluded,
the
branches are moved and artifact versions seem to be colliding. 2.0.4.x
seems
to work well for the stabilization purposes and it will allow to unblock
downstream and integration projects quickly.

Cos

Arun

On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:

All,

I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
The RC tag in svn is here:
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0

The maven artifacts are available via repository.apache.org.

Please try the release bits and vote; the vote will run for the usual
7 days.

Thanks for your voting
Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 04:08PM, Jean-Daniel Cryans wrote:
FWIW, not that I have a dog in this fight, but the only release with a
4th number (not including .0 like the 0.20.20x releases did) we had
was:

http://hadoop.6.n7.nabble.com/VOTE-Release-0-17-2-1-rc-0-td13398.html

0.17.2 was missing some native libs so 0.17.2.1 was released to fix
that critical issue instead of calling it .3

Exactly the point - the _bigfix_ release. Thanks for pointing out the
similarities.

Cos

J-D

On Thu, May 30, 2013 at 3:52 PM, Konstantin Boudnik c...@apache.org wrote:
On Thu, May 30, 2013 at 03:11PM, Matt Foley wrote:
Hi Cos,
I would also request that you renumber the release candidate to just
three-numbers, hence 2.0.5-alpha.

Arun, are you willing to start the 2.1.x name-space for your next release,
so that 2.0.x-alpha can become an intermediate stabilization branch as Cos
and Konst want?

Let's get the facts straight, Matt, please: this want has been expressed
in
the official vote here http://s.apache.org/ZMf Apparently, 2.0.5-alpha is
blocked now because of the another vote that hasn't been closed yet for
whatever reason. In order to unblock a number of releases in downstream
component I have moved forward with this release. Do you have any material
objections to the release that pursue this goal?

I dare to remind that forth part of the version is reserved - not in a
parallel universe, of course - for patch level aka bug fixes. It hardly
can
be taken a sign of 'forking' by any definition.

Cos

So, would you please consider using 2.0.5-alpha?

Thanks,
--Matt

On Thu, May 30, 2013 at 11:52 AM, Konstantin Boudnik c...@apache.org
wrote:

On Thu, May 30, 2013 at 10:57AM, Arun C Murthy wrote:
I see you just re-opened MAPREUDCE-5211.

Why not include MAPREDUCE-5211 as well rather than create one release
per patch?

Arun, it is unclear if MAPREDUCE-5211 has implications in 2.0.4 as per

https://issues.apache.org/jira/browse/MAPREDUCE-5211?focusedCommentId=13670574page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13670574

Hence, there's a good chance that it never will be backported. And I
don't
have any plans to created 'a release per patch'.

Also, this is the first time we are seeing a four-numbered scheme in
Hadoop.
Why not call this 2.0.5-alpha?

There were precedents in four-numbered schemes before: 0.20.20[3-5].0
comes to
mind.

As for 2.0.5-alpha: The release numbering games and votes that had
happened in
the last few weeks are very confusing. Some of them never been concluded,
the
branches are moved and artifact versions seem to be colliding. 2.0.4.x
seems
to work well for the stabilization purposes and it will allow to unblock
downstream and integration projects quickly.

Cos

Arun

On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:

All,

I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
The RC tag in svn is here:
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0

The maven artifacts are available via repository.apache.org.

Please try the release bits and vote; the vote will run for the usual
7 days.

Thanks for your voting
Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 05:30PM, Chris Douglas wrote:
 On Thu, May 30, 2013 at 3:25 PM, Konstantin Boudnik c...@apache.org wrote:
  There's no plans to release anything else at this point - this is a bug-fix
  release, as I pointed out on a numerous occasions. There's no new features -
  just 2 fixes.
 
 If you're worried about extending the voting by a week, I don't think
 anyone can reasonably object to a truncated schedule if the only
 change is the version number. Downstream fixes discovered in Bigtop
 are a sufficient reason for a patch release and I think we'd all like
 them to become routine. Not just in 2.0.x, but in later release
 branches.

I have no issues of changing the version to 2.0.5-alpha and restarting to vote
for the release content, e.g. 2 bug fixes. Shall I call 3 days re-vote because
of the number change?

  2.0.5 matter became and still is too controversial at some point. The vote
  started by Arun to override the results of the Konstantin's vote never been
  closed.
 
 For the nth time, neither release plan vote was binding. We recently
 amended the bylaws to eliminate this confusion. There is no ambiguity
 between votes when neither is in scope.

Does the result of bylaw vote nullifies the unfinished vote started by Arun?
Sorry, I am dense, apparently.

  The downstream projects are handing in the middle of the air because
  of that confusion.
 
 Can we please ground our discussion when discussing compatibility and
 bugs? Breathless alarm is not proportional to the severity, here.

Good point. Can we limit the vote thread to the merits of the release then?

  Have I missed something or you just called me a cheater and a lair right to 
  my face?
 
 I called you neither. The prenominate votes were closed, counted, and
 declared to be binding over objections. I'm annoyed that I have to
 toggle my vote to prevent that tactic, but based on recent experience
 I don't expect you to forgo it. I'd be happy to learn my caution is
 unnecessary. -C

That sound like adding an insult to injury, if my forth-language skills do not
mislead me.

Cos

   On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote:
   On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com 
   wrote:
Why not include MAPREDUCE-4211 as well rather than create one release 
per patch?
  
   From Cos's description, it sounded like these were backports of fixes
   to help Sqoop2 and fix some build issues. If it's not just to fixup
   leftover bugs in 2.0.4 *once* so downstream projects can integrate
   against 2.0.4.1, and this a release series, then I've completely
   misunderstood the purpose.
  
   Cos, are you planning 2.0.4.2?
  
Also, this is the first time we are seeing a four-numbered scheme in 
Hadoop. Why not call this 2.0.5-alpha?
  
   Good point. Since it contains only backports from branch-2, it would
   make sense for it to be an intermediate release.
  
   I shouldn't have to say this, but I'm changing my vote to -1 while we
   work this out. -C
  
On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:
   
All,
   
I have created a release candidate (rc0) for hadoop-2.0.4.1-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/hadoop-2.0.4.1-alpha-rc0/
The RC tag in svn is here: 
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4.1-alpha-rc0
   
The maven artifacts are available via repository.apache.org.
   
Please try the release bits and vote; the vote will run for the 
usual 7 days.
   
Thanks for your voting
 Cos

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha