hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Inder.dev Java" <java.in...@gmail.com>
Subject Re: 0.23.3 release coming soon
Date Thu, 23 Aug 2012 21:52:53 GMT
> We also wanted to do this out in the open so the community
could see what was happening, instead of in some private git repository.

You mean, you have some different changes in 23.3,  which is not put into
hadoop-2 ?

Note that, end of the day, ultimately community has to mark hadoop-2 as
stable. but not 23.3..versions right.

alpha cuts already going on and ppl are testing. If you find any bug in
23.3, you may contribute to hadoop-2.
That changes will be tested in next alpha cut right. If you test with 23.3
and say it is stable with out merging some things from hadoop-2, that will
not really give confidence on hadoop-2 releases right. If you are porting
everything from hadoop-2 to 23.3, then both releases are same. Need not
release it separately right? But I am not sure about it.

IMO, having official releases like this may confuse ppl differently.


On Fri, Aug 24, 2012 at 3:04 AM, Robert Evans <evans@yahoo-inc.com> wrote:

> There was a discussion about this in April
> http://mail-archives.apache.org/mod_mbox/hadoop-general/201204.mbox/%3CCB9F
> 2CBB.37CD3%25evans@yahoo-inc.com%3E
> in which there was unanimous approval of the idea.  I realize that it is
> confusing and I feel your pain.  I hate having to explain to our customers
> why we are going "backwards" from 1.0 to 0.23.
> The community as a whole is working hard and is serious about stabilizing
> hadoop-2.  As I said in the original proposal everything that is in 0.23.3
> has been merged first to branch-2.
> What is more, putting on my Yahoo hat, we have nightly builds and tests of
> branch-2.  We want to move to branch-2 as soon as possible, but to meet
> our goals to have YARN out in production by the end of this year we had to
> cut somewhere.  We also wanted to do this out in the open so the community
> could see what was happening, instead of in some private git repository.
> If the community has changed their mind and having an official release
> labeled 0.23 is too confusing to customers I am happy to not call a vote,
> but simply renumber the release and move on.
> --Bobby Evans
> On 8/23/12 4:09 PM, "Inder.dev Java" <java.inder@gmail.com> wrote:
> >Having releases like this kind of versions (back to 2x.x..) may confuse
> >people?
> >Hadoop-2 and 23.x may not have big difference right.
> >
> >already community decided to make the branches as 1, 2....etc.. So again
> >going back to 2x.x releases may really confuse people. I confused by
> >seeing
> >this release mail here.
> >
> >Why can't people put real effort on hadoop-2 itself and make it stable as
> >that is the version community wanted to make it stable from alpha? Why
> >this
> >effort split here.
> >
> >-thx
> >
> >On Fri, Aug 24, 2012 at 2:22 AM, Robert Evans <evans@yahoo-inc.com>
> wrote:
> >>
> >>
> >> I am planning to do cut a release candidate of 0.23.3 in the next week
> >>or
> >> so.  I am waiting for a few more JIRAs to go in (MAPREDUCE-3943 and
> >> HDFS-3177), and a bit more testing before I call a vote.  I know not too
> >> many people have been putting things into branch-0.23 directly, but if
> >>you
> >> do want to please check with me first. After I cut the release I will
> >>open
> >> the branch up again for more bug fixes for a 23.4 release.  I expect
> >>0.23.4
> >> to come about a month after 0.23.3. This is to incorporate any bug fixes
> >> needed as Yahoo! and hopefully others do more testing on 0.23.3 and
> >>start
> >> rolling it out to more clusters.
> >>
> >> --Bobby Evans
> >>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message