accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <>
Subject Re: [DISCUSS] Dev branches reflecting minor/major versions, not bugfixes
Date Mon, 12 May 2014 17:42:06 GMT
I think Joey hit the point best: the big change would be the shift to
short-lived bugfix branches for immediate release and more regular
release cadence, and long-lived branches would be for active
development on major/minor releases.

Christopher L Tubbs II

On Mon, May 12, 2014 at 10:42 AM, Keith Turner <> wrote:
> On Sun, May 11, 2014 at 6: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.
> Are you thinking that 1.6.1-SNAPSHOT would be created for the 1st bug that
> warrants it?
>> 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