From dev-return-19795-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Tue Jun 12 01:52:32 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DDFB4180647 for ; Tue, 12 Jun 2018 01:52:31 +0200 (CEST) Received: (qmail 94631 invoked by uid 500); 11 Jun 2018 23:52:30 -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 94620 invoked by uid 99); 11 Jun 2018 23:52:30 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2018 23:52:30 +0000 Received: from mail-qt0-f175.google.com (mail-qt0-f175.google.com [209.85.216.175]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id EBBC42B00 for ; Mon, 11 Jun 2018 23:52:29 +0000 (UTC) Received: by mail-qt0-f175.google.com with SMTP id l10-v6so16900327qtj.0 for ; Mon, 11 Jun 2018 16:52:29 -0700 (PDT) X-Gm-Message-State: APt69E2yAScFyJX4iVGJ1DEaNosOPi/E+RT9tLy+RrxoVxyZ8+3462f2 XRgEL7BjmYaQxRrfuvD2cJYXEmWkbqfqGnRj+bI= X-Google-Smtp-Source: ADUXVKKiVA7Fbk/MiRIHEde4hYfhbKOn9RIAGD0r4a72bsDiyCt0Londn88fEQd8j0RKNNMj8jqVv/9aufoNVikrEPA= X-Received: by 2002:a0c:90e1:: with SMTP id p88-v6mr1250932qvp.145.1528761149341; Mon, 11 Jun 2018 16:52:29 -0700 (PDT) MIME-Version: 1.0 References: <1430bf1e-0c3f-e1b3-aef8-dfd0f1f0e11a@apache.org> In-Reply-To: From: Christopher Date: Mon, 11 Jun 2018 19:52:17 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Draft release timeline for 2.0.0 To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary="00000000000040cb9b056e66710e" --00000000000040cb9b056e66710e Content-Type: text/plain; charset="UTF-8" I do not expect that page to be a complete or final set of features right now, but it's probably better than the issue tracker is (because of all the noise of old issues). Part of the goal of this thread was to motivate people to start finalizing that set over the next few weeks as they triage open issues and think about what they can realistically finish in the timeline we establish. The hope is that the page will become more and more complete as head more strongly towards this release. As for the timeline, I have no problem moving the time table up if we get a bit further along and realize we're in a good place to release. I just don't like the pressure of unrealistically short timelines, and I know that personally, my summer is going to be very busy regardless. Initially, I was hoping we could release around September 1st... but then I figured add a month for dedicated testing and documentation might be nice... and we'd still release before the summit. On Mon, Jun 11, 2018 at 6:36 PM Josh Elser wrote: > Based on that, https://issues.apache.org/jira/browse/ACCUMULO-4733 is > the only thing outstanding (and just one question at that). > > Mid/late August seems like a long time until feature-complete for > essentially a no-op of work :) > > On 6/11/18 5:07 PM, Christopher wrote: > > I believe those are being maintained in the draft release notes at > > https://accumulo.apache.org/release/accumulo-2.0.0/ > > > > On Mon, Jun 11, 2018 at 5:02 PM Josh Elser wrote: > > > >> What are the current 2.0.0 features? (Outstanding and completed) > >> > >> On 6/11/18 4:35 PM, Christopher wrote: > >>> Hi Accumulo Devs, > >>> > >>> I've been thinking about the 2.0.0 release timeline. I was thinking > >>> something like this milestone timeline: > >>> > >>> Feature Complete : mid-late August > >>> Dedicated Testing, Documentation, and release voting : all of September > >>> Final release : October 1st > >>> > >>> This schedule would make 2.0.0 available for the Accumulo Summit coming > >> up > >>> in October, with a few weeks to spare. > >>> > >> > > > --00000000000040cb9b056e66710e--