You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by John Vines <vi...@apache.org> on 2013/09/27 19:39:36 UTC
[VOTE] 1.6.0 Feature freeze.
Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
and increment the version in master. "Feature Freeze" means only bug fixes
and documentation updates happen after the date, which implies major code
additions and changes are already in place with appropriate tests.
If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
release, they should bring it up on the dev list. If agreement can not be
reached on the dev list with 72 hours, then the commiter can call for a
vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
majority approval[1]. If the vote passes, any commiter can revert the
feature from 1.6.0-SNAPSHOT.
This vote will remain open for 72 hours and must have consensus approval[2]
to pass.
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Josh Elser <jo...@gmail.com>.
+1
On Sep 27, 2013 11:40 AM, "John Vines" <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by John Vines <vi...@apache.org>.
+1 (binding)
And thanks for tacking those links on, Sean
On Fri, Sep 27, 2013 at 2:01 PM, Joey Echeverria <jo...@cloudera.com> wrote:
> +1 (non-binding)
>
> On Fri, Sep 27, 2013 at 1:58 PM, Sean Busbey <bu...@cloudera.com> wrote:
> > +1 (non-binding)
> >
> >
> > On Fri, Sep 27, 2013 at 12:57 PM, Sean Busbey <bu...@cloudera.com>
> wrote:
> >
> >> I presume the appropriate links are:
> >>
> >> [1]:http://www.apache.org/foundation/glossary.html#MajorityApproval
> >> [2]:http://www.apache.org/foundation/glossary.html#ConsensusApproval
> >>
> >>
> >> On Fri, Sep 27, 2013 at 12:39 PM, John Vines <vi...@apache.org> wrote:
> >>
> >>> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> >>> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from
> master
> >>> and increment the version in master. "Feature Freeze" means only bug
> >>> fixes
> >>> and documentation updates happen after the date, which implies major
> code
> >>> additions and changes are already in place with appropriate tests.
> >>>
> >>> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> >>> release, they should bring it up on the dev list. If agreement can
> not be
> >>> reached on the dev list with 72 hours, then the commiter can call for a
> >>> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
> >>> with
> >>> majority approval[1]. If the vote passes, any commiter can revert the
> >>> feature from 1.6.0-SNAPSHOT.
> >>>
> >>> This vote will remain open for 72 hours and must have consensus
> >>> approval[2]
> >>> to pass.
> >>>
> >>
> >>
> >>
> >> --
> >> Sean
> >>
> >
> >
> >
> > --
> > Sean
>
>
>
> --
> Joey Echeverria
> Director, Federal FTS
> Cloudera, Inc.
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Joey Echeverria <jo...@cloudera.com>.
+1 (non-binding)
On Fri, Sep 27, 2013 at 1:58 PM, Sean Busbey <bu...@cloudera.com> wrote:
> +1 (non-binding)
>
>
> On Fri, Sep 27, 2013 at 12:57 PM, Sean Busbey <bu...@cloudera.com> wrote:
>
>> I presume the appropriate links are:
>>
>> [1]:http://www.apache.org/foundation/glossary.html#MajorityApproval
>> [2]:http://www.apache.org/foundation/glossary.html#ConsensusApproval
>>
>>
>> On Fri, Sep 27, 2013 at 12:39 PM, John Vines <vi...@apache.org> wrote:
>>
>>> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
>>> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
>>> and increment the version in master. "Feature Freeze" means only bug
>>> fixes
>>> and documentation updates happen after the date, which implies major code
>>> additions and changes are already in place with appropriate tests.
>>>
>>> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
>>> release, they should bring it up on the dev list. If agreement can not be
>>> reached on the dev list with 72 hours, then the commiter can call for a
>>> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
>>> with
>>> majority approval[1]. If the vote passes, any commiter can revert the
>>> feature from 1.6.0-SNAPSHOT.
>>>
>>> This vote will remain open for 72 hours and must have consensus
>>> approval[2]
>>> to pass.
>>>
>>
>>
>>
>> --
>> Sean
>>
>
>
>
> --
> Sean
--
Joey Echeverria
Director, Federal FTS
Cloudera, Inc.
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Sean Busbey <bu...@cloudera.com>.
+1 (non-binding)
On Fri, Sep 27, 2013 at 12:57 PM, Sean Busbey <bu...@cloudera.com> wrote:
> I presume the appropriate links are:
>
> [1]:http://www.apache.org/foundation/glossary.html#MajorityApproval
> [2]:http://www.apache.org/foundation/glossary.html#ConsensusApproval
>
>
> On Fri, Sep 27, 2013 at 12:39 PM, John Vines <vi...@apache.org> wrote:
>
>> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
>> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
>> and increment the version in master. "Feature Freeze" means only bug
>> fixes
>> and documentation updates happen after the date, which implies major code
>> additions and changes are already in place with appropriate tests.
>>
>> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
>> release, they should bring it up on the dev list. If agreement can not be
>> reached on the dev list with 72 hours, then the commiter can call for a
>> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
>> with
>> majority approval[1]. If the vote passes, any commiter can revert the
>> feature from 1.6.0-SNAPSHOT.
>>
>> This vote will remain open for 72 hours and must have consensus
>> approval[2]
>> to pass.
>>
>
>
>
> --
> Sean
>
--
Sean
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Sean Busbey <bu...@cloudera.com>.
I presume the appropriate links are:
[1]:http://www.apache.org/foundation/glossary.html#MajorityApproval
[2]:http://www.apache.org/foundation/glossary.html#ConsensusApproval
On Fri, Sep 27, 2013 at 12:39 PM, John Vines <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
>
--
Sean
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Christopher <ct...@apache.org>.
+1
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Fri, Sep 27, 2013 at 1:39 PM, John Vines <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Keith Turner <ke...@deenlo.com>.
+1
On Fri, Sep 27, 2013 at 1:39 PM, John Vines <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Eric Newton <er...@gmail.com>.
+1
On Fri, Sep 27, 2013 at 1:39 PM, John Vines <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Corey Nolet <cj...@gmail.com>.
+1
On Sat, Sep 28, 2013 at 2:04 PM, William Slacum <
wilhelm.von.cloud@accumulo.net> wrote:
> Plus One
>
>
> On Fri, Sep 27, 2013 at 5:02 PM, Mike Drob <md...@mdrob.com> wrote:
>
> > +1
> >
> >
> > On Fri, Sep 27, 2013 at 4:02 PM, Brian Loss <bf...@praxiseng.com>
> wrote:
> >
> > > +1
> > >
> > > On Sep 27, 2013, at 1:39 PM, John Vines <vi...@apache.org>
> > > wrote:
> > >
> > > > Please vote on a feature freeze date of Nov 1 23:59 PDT for the
> master
> > > > branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from
> > > master
> > > > and increment the version in master. "Feature Freeze" means only bug
> > > fixes
> > > > and documentation updates happen after the date, which implies major
> > code
> > > > additions and changes are already in place with appropriate tests.
> > > >
> > > > If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> > > > release, they should bring it up on the dev list. If agreement can
> not
> > > be
> > > > reached on the dev list with 72 hours, then the commiter can call
> for a
> > > > vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must
> pass
> > > with
> > > > majority approval[1]. If the vote passes, any commiter can revert
> the
> > > > feature from 1.6.0-SNAPSHOT.
> > > >
> > > > This vote will remain open for 72 hours and must have consensus
> > > approval[2]
> > > > to pass.
> > >
> > >
> >
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by William Slacum <wi...@accumulo.net>.
Plus One
On Fri, Sep 27, 2013 at 5:02 PM, Mike Drob <md...@mdrob.com> wrote:
> +1
>
>
> On Fri, Sep 27, 2013 at 4:02 PM, Brian Loss <bf...@praxiseng.com> wrote:
>
> > +1
> >
> > On Sep 27, 2013, at 1:39 PM, John Vines <vi...@apache.org>
> > wrote:
> >
> > > Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> > > branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from
> > master
> > > and increment the version in master. "Feature Freeze" means only bug
> > fixes
> > > and documentation updates happen after the date, which implies major
> code
> > > additions and changes are already in place with appropriate tests.
> > >
> > > If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> > > release, they should bring it up on the dev list. If agreement can not
> > be
> > > reached on the dev list with 72 hours, then the commiter can call for a
> > > vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
> > with
> > > majority approval[1]. If the vote passes, any commiter can revert the
> > > feature from 1.6.0-SNAPSHOT.
> > >
> > > This vote will remain open for 72 hours and must have consensus
> > approval[2]
> > > to pass.
> >
> >
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Mike Drob <md...@mdrob.com>.
+1
On Fri, Sep 27, 2013 at 4:02 PM, Brian Loss <bf...@praxiseng.com> wrote:
> +1
>
> On Sep 27, 2013, at 1:39 PM, John Vines <vi...@apache.org>
> wrote:
>
> > Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> > branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from
> master
> > and increment the version in master. "Feature Freeze" means only bug
> fixes
> > and documentation updates happen after the date, which implies major code
> > additions and changes are already in place with appropriate tests.
> >
> > If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> > release, they should bring it up on the dev list. If agreement can not
> be
> > reached on the dev list with 72 hours, then the commiter can call for a
> > vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
> with
> > majority approval[1]. If the vote passes, any commiter can revert the
> > feature from 1.6.0-SNAPSHOT.
> >
> > This vote will remain open for 72 hours and must have consensus
> approval[2]
> > to pass.
>
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Brian Loss <bf...@praxiseng.com>.
+1
On Sep 27, 2013, at 1:39 PM, John Vines <vi...@apache.org>
wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
Re: [VOTE] 1.6.0 Feature freeze.
Posted by John Vines <vi...@apache.org>.
It's been 72 hours and we have 10 binding + 2 non-binding votes, with none
against. So November 1 at 23:59 PDT we will feature freeze with the above
conditions. We are approximately 1 month out and I will send out reminders
as we approach the deadline.
On Sat, Sep 28, 2013 at 9:29 PM, Adam Fuchs <af...@apache.org> wrote:
> +1
> On Sep 27, 2013 1:40 PM, "John Vines" <vi...@apache.org> wrote:
>
> > Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> > branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from
> master
> > and increment the version in master. "Feature Freeze" means only bug
> fixes
> > and documentation updates happen after the date, which implies major code
> > additions and changes are already in place with appropriate tests.
> >
> > If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> > release, they should bring it up on the dev list. If agreement can not
> be
> > reached on the dev list with 72 hours, then the commiter can call for a
> > vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass
> with
> > majority approval[1]. If the vote passes, any commiter can revert the
> > feature from 1.6.0-SNAPSHOT.
> >
> > This vote will remain open for 72 hours and must have consensus
> approval[2]
> > to pass.
> >
>
Re: [VOTE] 1.6.0 Feature freeze.
Posted by Adam Fuchs <af...@apache.org>.
+1
On Sep 27, 2013 1:40 PM, "John Vines" <vi...@apache.org> wrote:
> Please vote on a feature freeze date of Nov 1 23:59 PDT for the master
> branch. Shortly after this time we will branch 1.6.0-SNAPSHOT from master
> and increment the version in master. "Feature Freeze" means only bug fixes
> and documentation updates happen after the date, which implies major code
> additions and changes are already in place with appropriate tests.
>
> If a commiter thinks a new feature in 1.6.0-SNAPSHOT is not ready for
> release, they should bring it up on the dev list. If agreement can not be
> reached on the dev list with 72 hours, then the commiter can call for a
> vote on reverting the feature from 1.6.0-SNAPSHOT. The vote must pass with
> majority approval[1]. If the vote passes, any commiter can revert the
> feature from 1.6.0-SNAPSHOT.
>
> This vote will remain open for 72 hours and must have consensus approval[2]
> to pass.
>