Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> Accumulo feature freeze in 1 week


Copy link to this message
-
Re: Accumulo feature freeze in 1 week
I applied the patch in
https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=789c920 (commented
on the ticket).  I've just left it open so we could decide what to do about
different exit codes.
On Mon, Oct 28, 2013 at 2:39 AM, Steve Loughran <[EMAIL PROTECTED]>wrote:

> I'd like this patch looked at; makes it easier to integrate accumulo with
> scripts and controllers, as they can different failures from other outcomes
>
> https://issues.apache.org/jira/browse/ACCUMULO-1709
>
>
> On 26 October 2013 03:30, John Vines <[EMAIL PROTECTED]> wrote:
>
> > 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
> > 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 <[EMAIL PROTECTED]>
> > 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 <[EMAIL PROTECTED]>
> > >> 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 <[EMAIL PROTECTED]>
> > >> 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
> > >>
> > >
> > >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader