Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
Reply-To: vines@apache.org
In-Reply-To: 
 <CADczPYRgZ84Z9uW1hBr=ggnCokJcDg=vOnuTG3jRe5eQPaWQug@mail.gmail.com>
References: 
 <CADczPYScid=9K6uABF1O+O8XX21kFYGJQcAbx666ma3k2H0u3Q@mail.gmail.com>
 <CAL5zq9aRfbKxCBYiqjDiUw1my9-BDMvXBty=UiUZe2nf7h-wHg@mail.gmail.com>
 <CADczPYSuVpwNkjXuFsQZegLy4oAs209h0akvXkkejd8Ys+cZ0Q@mail.gmail.com>
 <526AC343.2020801@gmail.com>
 <CAGHyZ6+MrSfWkPq0ucLM67ao3a=4kwEYPexB2hbUx1tyOpEjyA@mail.gmail.com>
 <CADczPYRgZ84Z9uW1hBr=ggnCokJcDg=vOnuTG3jRe5eQPaWQug@mail.gmail.com>
From: John Vines <vines@apache.org>
Date: Fri, 25 Oct 2013 22:30:10 -0400
Message-ID: 
 <CADczPYRhA7fz3YS6gUOes63_BZSmWi7DP4QqBEOB6otz6C6F5Q@mail.gmail.com>
Subject: Re: Accumulo feature freeze in 1 week
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary=089e013d1866c596e904e99ba7cf

--089e013d1866c596e904e99ba7cf
Content-Type: text/plain; charset=ISO-8859-1

I went ahead and did one pass, there are 156 of them, 14 of which labelled
for Documentation. That's 142 at varying levels. I have 15 tabs of tickets
I will take a stab at over the next week. If everyone can identify tickets
that they plan to work on this last week so a good idea of what's in
progress can be identified, that would be stellar. I'm going to do another
pass through Monday afternoon with a stronger hand to pare down the list,
ideally to under 75.


On Fri, Oct 25, 2013 at 4:26 PM, John Vines <vines@apache.org> wrote:

> I'm going to start going through 1.6 tickets and either bump them to 1.7
> or question if they should slip if I need more information.
>
>
> On Fri, Oct 25, 2013 at 4:20 PM, Sean Busbey <busbey@cloudera.com> wrote:
>
>> We should probably declare a release manager for 1.6.0. I don't think the
>> feature freeze vote set one (future ones probably should).
>>
>>
>> Then they can start pinging people to find out where we are on the
>> blockers.
>>
>> -Sean
>>
>>
>> On Fri, Oct 25, 2013 at 2:15 PM, Josh Elser <josh.elser@gmail.com> wrote:
>>
>> > True, but at the same time it makes no sense to release 1.6.0 if the
>> > features contained within are incomplete.
>> >
>> > There are still a number of blockers that are unresolved that would all
>> > fall into the category of creating a broken 1.6.0 or having to back out
>> > large changesets. I know these blockers would be categorized as "bug
>> fixes"
>> > and not "features", but some of these bugs are directly from new
>> features
>> > which I would argue are thus still a part of this feature.
>> >
>> > I'm all for trying to release early and often, but I will be the guy who
>> > throws a wrench in the works if we do it at the sake of reducing the
>> > quality of our release.
>> >
>> >
>> > On 10/25/13 11:49 AM, John Vines wrote:
>> >
>> >> I'd rather not go down the slippery slope we went down last time. I'll
>> >> gladly be the bad guy and say that things are getting pushed to 1.7.
>> >>
>> >>
>> >> On Fri, Oct 25, 2013 at 2:23 PM, Christopher <ctubbsii@apache.org>
>> wrote:
>> >>
>> >>  It looks like we're 50% in terms of tickets complete.
>> >>>
>> >>> http://s.apache.org/accumulo-**1.6.0-issues<
>> http://s.apache.org/accumulo-1.6.0-issues>
>> >>>
>> >>> Extensions are always nice, but I'm not going to be the bad guy and
>> >>> ask for one :)
>> >>>
>> >>> --
>> >>> Christopher L Tubbs II
>> >>> http://gravatar.com/ctubbsii
>> >>>
>> >>>
>> >>> On Fri, Oct 25, 2013 at 12:33 PM, John Vines <vines@apache.org>
>> wrote:
>> >>>
>> >>>> Alright folks, we're down to the wire. Feature freeze is one week
>> away.
>> >>>>
>> >>> If
>> >>>
>> >>>> anyone has any last minute concerns about this schedule, please
>> speak up
>> >>>> now. Otherwise, have a great weekend!
>> >>>>
>> >>>
>> >>>
>> >>
>>
>>
>> --
>> Sean
>>
>
>

--089e013d1866c596e904e99ba7cf--