incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé <>
Subject Re: Cutting new branch to work on 0.3.1 release (Hadoop 1.1 line)
Date Sun, 08 Jul 2012 01:26:06 GMT
On 07/07/2012 06:16 PM, Konstantin Boudnik wrote:
> On Sat, Jul 07, 2012 at 06:12PM, Bruno Mahé wrote:
>> On 07/07/2012 06:08 PM, Konstantin Boudnik wrote:
>>> Guys,
>>> I'd like to cut new release branch for future BigTop 0.3.1 that is going to be
>>> based on Hadoop 1.1
>>> Any objections?
>>> Cos
>> +1 provided patches in branch-0.3.1 would also be in branch-0.3
>> (surely a given, but it is better to clarify).
> actually, it seems like a bit of double work. The purpose of having a separate
> release branch is to well... separate the states of 0.3 and 0.3.1 release,
> because the latter might include a different set of component version (from
> have been in 0.3). backporting such patches would I am sure create quite a
> confusion. Don't you think?
> Cos

Unless I am missing something, a 0.3.1 branch should only exist in order 
to stabilize the 0.3 branch for the coming release.
So any additional work on 0.3 out of scope for the 0.3.1 can still be 
checked in and be part of a 0.3.2 release (ex: I want to backport giraph 
or add some other project to the 0.3 branch, outside of the BOM of 
0.3.1). But any bugfix in 0.3.1 would still be needed for any future 0.3 
branch. And as well, any version 0.3.2 should contain the same set of 
components at the same version or later than the ones in 0.3.1.

If we are not at the point where new features in branch-0.3 can 
interfere with the stabilization of 0.3.1, branching for 0.3.1 can 
probably be delayed.


View raw message