accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joey Echeverria <>
Subject Re: [DISCUSS] Dev branches reflecting minor/major versions, not bugfixes
Date Mon, 12 May 2014 14:19:03 GMT
On Mon, May 12, 2014 at 10:08 AM, Alex Moundalexis
<> wrote:
> To confirm, a bug fix release will just cut from whatever specific commit
> is selected by the proposer?

My read is that if there were issues fixed in 1.7.0-SNAPSHOT that
would warrant a 1.6.1 release, then a new branch would be made, those
issues would be fixed in the branch, and then a release would be cut.
Basically, this would change from having long-lived bug fix branches
to just-in-time branches specifically for a bug fix release.


> On Sun, May 11, 2014 at 3:15 PM, Christopher <> wrote:
>> Accumulo developers:
>> As part of our transition to better versioning standards, and more
>> regular releases, with better release planning, I was thinking that
>> our development branches should generally reflect an anticipated
>> minor/major release version, and not an expected bugfix version. It
>> seems to me that we should focus active development on minor/major
>> releases, and branch for bugfix releases temporarily, only to push out
>> an important bugfix.
>> With that in mind, I'd like to change the current 1.6.1-SNAPSHOT to
>> 1.7.0-SNAPSHOT in expectation for a forthcoming minor release (we
>> would have to discuss what kinds of things we'd want in such a
>> release. Minimally, I want ACCUMULO-1691), and the master branch to
>> 2.0.0 for development on the next major release.
>> If there's any outstanding bugfixes in the 1.6.1-SNAPSHOT branch that
>> would warrant a separate bugfix release, I think we should discuss
>> them and plan for a 1.6.1 within a month or so (along with a 1.5.2).
>> I'd like to discuss this here a bit and see if this makes sense before
>> initiating a vote on it.
>> --
>> Christopher L Tubbs II

View raw message