hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: Vote on 0.20.3.1
Date Wed, 07 Apr 2010 20:35:12 GMT
What happens if we need to patch 0.20.4?  And make a new release based
on 0.20.4 but in 2 weeks but not before the 0.20 branch is ready?

How can we guarantee that this won't happen?


On Wed, Apr 7, 2010 at 1:29 PM, Jonathan Gray <jgray@facebook.com> wrote:
> The issue would be that we break out 0.20.4 to make an RC.  Now we have to
> patch 3 separate trees for each bug fix (0.20.4, 0.20.5, and 0.21).
>
> Even given that, I'm still +1 on moving ahead with this plan.  Once we
> release 0.20.4, dev goes back to how we are operating now against branch and
> trunk.
>
> JG
>
> On 4/7/10 12:57 PM, "Andrew Purtell" <apurtell@apache.org> wrote:
>
>> I thought we agreed no third branch. What we are discussing now is 0.20.4.
>> Everything else is 0.20.5.
>>
>> If 0.20.4 release is 0.20.4-dev minus some changes, but 0.20.5 (and
>> 0.20.5-dev) is whatever went into 0.20.4 plus what was left out, then there is
>> some temporary discontinuity on the branch at the release (elided commits) but
>> that is immediately healed after the release when 0.20.5-dev is opened. So
>> from the users point of view there is no discontinuity. Trouble with 0.20.4?
>> Fix in 0.20.5-dev per usual. Or am I missing something?
>>
>>> From: Ryan Rawson <ryanobjc@gmail.com>
>>> Subject: Re: Vote on 0.20.3.1
>>> To: hbase-dev@hadoop.apache.org
>>> Date: Wednesday, April 7, 2010, 12:16 PM
>>> If we made a 3rd branch we now have 3 hbase versions with 3
>>> distinct code lineages.  Will we patch this new 0.20.4 version
>>> as bugs come up?
>>
>>
>>
>>
>>
>
>

Mime
View raw message