Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2BCD110E4C for ; Mon, 28 Oct 2013 09:40:15 +0000 (UTC) Received: (qmail 39370 invoked by uid 500); 28 Oct 2013 09:40:14 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 39283 invoked by uid 500); 28 Oct 2013 09:40:04 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 39270 invoked by uid 99); 28 Oct 2013 09:40:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 09:40:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stevel@hortonworks.com designates 209.85.212.49 as permitted sender) Received: from [209.85.212.49] (HELO mail-vb0-f49.google.com) (209.85.212.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Oct 2013 09:39:57 +0000 Received: by mail-vb0-f49.google.com with SMTP id w16so4171287vbb.22 for ; Mon, 28 Oct 2013 02:39:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=RqyzDSHcN4k2Ojtwf4mQgrppU+3ldnSgU27B5oRzXbo=; b=Sh+neM75hHvx2JxKGRdV3f0fYGF8wnkFpDhD30yeUA2oZS6jy93rjTADjEre4xunED Modnc++aicBgh9V/6Qz3JVN0oDOKucvUJxAC29Vs8QqETQ2T8ZwjbBSV8m1u8cWryi1J DLJQ0iJRAuvPejYzRVDwcnMJ2vNexG0hBgiCYlPLs3B5fO9wy716EhqZ7FHhf6U2nD/5 W/iOcbOTeO3tKSnhlFds1k7QLz2b2dTGAEXM4IoDEEX5vn6oFWi3UYJZ2enNJHI8D+t2 tqkdskbW2bFFILm5RxeUOAswE3vHFw9EcSAojDKlfzwP8bTWv94w/VT+WS1xDgIUZvXd lL3w== X-Gm-Message-State: ALoCoQkOlzh7QiyB1IN3WT2JYZAvdiYE+/tY5yPt14IDHfOX4Teh46DsOBbREemw1A9skklvnwrRh8QN9gRiz3kmGi31u/+hwx0oMreZDJAI/RKq1XNpKlY= MIME-Version: 1.0 X-Received: by 10.221.27.73 with SMTP id rp9mr893605vcb.29.1382953176169; Mon, 28 Oct 2013 02:39:36 -0700 (PDT) Received: by 10.58.154.98 with HTTP; Mon, 28 Oct 2013 02:39:36 -0700 (PDT) In-Reply-To: References: <526AC343.2020801@gmail.com> Date: Mon, 28 Oct 2013 09:39:36 +0000 Message-ID: Subject: Re: Accumulo feature freeze in 1 week From: Steve Loughran To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary=001a11339706ce97d904e9c9e017 X-Virus-Checked: Checked by ClamAV on apache.org --001a11339706ce97d904e9c9e017 Content-Type: text/plain; charset=UTF-8 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 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 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 > 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 > 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 > >> 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 > >> 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 of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --001a11339706ce97d904e9c9e017--