Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HDFS >> mail # dev >> Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha


Copy link to this message
-
Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha
On the version number we use, if it is greater than 2.0.4, I really don't
care. Though I think Konstantin argument that branch-2 is publishing as
2.0.5-SNAPSHOT has some ground (still, it could be argued that they are DEV
JARs so they can be  in flux).

On the changes that went into this RC, they are exactly a fix for Sqoop2 to
work with the release and a build fix for Bigtop. As far as I can tell
there is nothing else in this RC as compared with 2.0.4-alpha.

So, effectively, this RC is just a fixup of 2.0.4 for Sqoop and Bigtop.

MAPREDUCE-5211 seems nasty enough to be included.

But I'd leave that to the RM (Cos in this case) to decide if  he wants to
go ahead without  it and then do a 2.0.4.2. Personally i would cut a second
RC including MAPREDUCE-5211. But I don't think that not having it would be
reason enough for a -1 (if that is the reason for the -1).

Thanks.
On Thu, May 30, 2013 at 1:48 PM, Chris Douglas <[EMAIL PROTECTED]> wrote:

> On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy <[EMAIL PROTECTED]>
> 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
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB