hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Douglas <cdoug...@apache.org>
Subject Re: abandoning 22 - was: Content request for 0.20.205 Sustaining Release
Date Tue, 06 Sep 2011 20:23:47 GMT
There is some confusion, here.

Nigel is the RM for the current 0.22 branch. If he abandons it then
that branch is done, but nobody has a lock on the next release. Any
committer can manage a branch, package its contents, and propose an
artifact. If it receives a majority of votes from the PMC, then it
becomes 0.22. Whether it's derived from the current 0.22 branch is up
to that RM.

Anyone keen to see a particular release must do the work to effect it.
We don't assign work by voting.

On Tue, Sep 6, 2011 at 12:08 PM,  <Milind.Bhandarkar@emc.com> wrote:
> AKAIK, the bylaws do not mention anything about "abandoning release". If
> past is any indication, even if releases 0.19.*, and 0.21.* were not
> adopted by large hadoop installations, these releases were cut, voted on,
> and approved. Not "abandoned".

To your point, a branch targeted as 0.21 was abandoned, despite months
of backporting changes from trunk. A branch containing subsequent work
was released instead. Whether the current 0.23 branch is released as
0.22 will depend exclusively on their respective effort and support.

Though you're right: this probably should be written into the bylaws,
even if any contrary model is illusory in practice. -C

Mime
View raw message