Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # dev >> Re: [VOTE] 0.23.3 release

Copy link to this message
Re: [VOTE] 0.23.3 release
Thanks for the info Owen I was not aware of that, I can see at the
beginning of the twiki
http://wiki.apache.org/hadoop/HowToReleasePostMavenization that it is kind
of implied by the skip this section comment.  But, I was just confused
because to do an official release I need to change the version number in
several different places, and I didn¹t think that is was all that kosher
to do that directly in the tags area.  It also seems to be a bit different
then what is happening on branch-2.




I was planning on deleting the branch once the vote for 0.23.3 finished,
but I can delete it now if you would prefer and the roll back the version
numbers on branch-0.23 to be 0.23.3? Or would it be 0.23.3-SNAPSHOT still?
 I also want to be sure that we want to not allow anyone to check anything
in for a week+ on branch-0.23.  There are a few things I know of that are
almost ready but are not Blockers.


On 9/10/12 12:33 PM, "Owen O'Malley" <[EMAIL PROTECTED]> wrote:

>On Fri, Sep 7, 2012 at 12:56 PM, Bobby Evans <[EMAIL PROTECTED]> wrote:
>> I have built an RC0 for 0.23.3 and am calling a vote on it
>Hi Bobby,
>   I noticed that you created a branch-0.23.3. The pattern we have
>used in Hadoop is that there is a release branch that is for a minor
>release (branch-0.23) and tags for the release candidates
>(release-0.23.3-rc0) and releases (release-0.23.3). Generally, the RM
>freezes the minor branch while they are trying to get the right set of
>patches together for the release candidate.
>-- Owen