Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CADczPYQ9PBuH8ZJLJ2mzHnW-os72LJboreadVtq==xb6VzPhwg@mail.gmail.com>
References: 
 <CADczPYQ9PBuH8ZJLJ2mzHnW-os72LJboreadVtq==xb6VzPhwg@mail.gmail.com>
Date: Wed, 2 Oct 2013 14:56:44 -0400
Message-ID: 
 <CAL5zq9Z_w-w3g16X8=rFPvHoNemnP3gS_fR1NGSb1jTBZjVukw@mail.gmail.com>
Subject: Re: [VOTE] 1.6.0 Feature freeze.
From: Christopher <ctubbsii@apache.org>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=UTF-8

+1

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Fri, Sep 27, 2013 at 1:39 PM, John Vines <vines@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.