Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CADczPYRcdVN8Pym6t3xNGoKpBn7F93VOEqLCPDPH0sOvVxStHA@mail.gmail.com>
References: 
 <CAGUtCHr9+8qRchrm99S9JEXo53tgte7FZGePkncXo-MZJkmh-Q@mail.gmail.com>
	<CADczPYRBF0H_fLjRMUqKz07sOkP03+HPYsoV8HEFj5tVbo8DOA@mail.gmail.com>
	<CAGUtCHpvO8Nf0Vv+dCUj9aXvwJ9+y0wOCA9MsTpKwbydVxtq6w@mail.gmail.com>
	<CADczPYRcdVN8Pym6t3xNGoKpBn7F93VOEqLCPDPH0sOvVxStHA@mail.gmail.com>
Date: Thu, 14 Feb 2013 15:09:08 -0500
Message-ID: 
 <CAGUtCHrw5xwi=kCD+i8Px=7Zqh61=SX52WaJqF6umkbWMJaU+w@mail.gmail.com>
Subject: Re: Branching 1.5
From: Keith Turner <keith@deenlo.com>
To: dev@accumulo.apache.org, vines@apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 14, 2013 at 2:53 PM, John Vines <vines@apache.org> wrote:
> I just don't understand the urgency to start adding new features to 1.6. If
> there's a standing patch, then we're in great shape for the second we do

>From the perspective of a non-committer I think it would be satisfying
to see your patch applied to svn.  I know when I have submitted
patches to other Apache projects it was satisfying to see it comitted.

I think we should encourage contributions and new feature development
at any point in time.
.
> But once we switch the trunk to 1.6, it does flag a lot of transition work
> to be done (version numbers, purging deprecated code, etc.)
>
>
> On Thu, Feb 14, 2013 at 2:45 PM, Keith Turner <keith@deenlo.com> wrote:
>
>> On Thu, Feb 14, 2013 at 2:20 PM, John Vines <vines@apache.org> wrote:
>> > I think we should hold off for a few days, perhaps a week or two, just so
>> > we have more time for bug squashing without concerns about merging bug
>> > fixes.
>>
>> I have also wanted to avoid doing this, I did not want to do until
>> there was a reason.  It has been 3 or 4 weeks since feature freeze.
>> While working on the recent patch from Damon I was thinking I would
>> like to put this in svn when its ready.  But I am not sure if it
>> should go in 1.5.  Its not a bug fix.  I would like to avoid having
>> discussions about what to do about every non bug fix.   I am thinking
>> avoiding these discussions may save us more time than merging.
>>
>> It should be very easy to automatically merge all changes from 1.5 to
>> trunk as long as no one make massive changes to trunk.  I can take
>> point on doing this until we release 1.5.0.  I will make sure all bug
>> fixes in 1.5 branch end up in trunk.
>>
>> What do you think?
>>
>> >
>> >
>> > On Thu, Feb 14, 2013 at 2:13 PM, Keith Turner <keith@deenlo.com> wrote:
>> >
>> >> I propose we branch 1.5.  We are passed the feature freeze for 1.5 and
>> >> it would be nice to be able to commit some recent contributions to
>> >> trunk.
>> >>
>> >> If no one objects I will create the branch Tuesday morning.
>> >>
>> >> Keith
>> >>
>>