From dev-return-19877-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Sat Oct 6 06:27:54 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 2D21418061A for ; Sat, 6 Oct 2018 06:27:54 +0200 (CEST) Received: (qmail 38556 invoked by uid 500); 6 Oct 2018 04:27:48 -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 38544 invoked by uid 99); 6 Oct 2018 04:27:47 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2018 04:27:47 +0000 Received: from mail-qk1-f179.google.com (mail-qk1-f179.google.com [209.85.222.179]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 0B81F146E for ; Sat, 6 Oct 2018 04:27:47 +0000 (UTC) Received: by mail-qk1-f179.google.com with SMTP id 12-v6so2341835qkj.10 for ; Fri, 05 Oct 2018 21:27:47 -0700 (PDT) X-Gm-Message-State: ABuFfognMeXiY7e97TXEjsJSZVmaKhoMWtObB6wRTA0ckMQQ/YeKMNVw qKLD9mgTioBT+xZcOYk9HsYy97Xo3mZJAJCpybk= X-Google-Smtp-Source: ACcGV62EjD6g4bOfoN3bc5BEUQpDUV1+BOb3vHRABQdhZYQP7ar5rkyoSTz0dPELLFcbGqbQlVIEiAXwYdvKpI7ZQYs= X-Received: by 2002:a37:17e4:: with SMTP id 97-v6mr11702136qkx.58.1538800066745; Fri, 05 Oct 2018 21:27:46 -0700 (PDT) MIME-Version: 1.0 From: Christopher Date: Sat, 6 Oct 2018 00:27:30 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISCUSS] 2.0.0-alpha? To: accumulo-dev Content-Type: text/plain; charset="UTF-8" Hi Accumulo devs, I'm thinking about initiating a vote next week for a 2.0.0-alpha release, so we can have an official ASF release (albeit without the usual stability expectations as a normal release) to be available for the upcoming Accumulo Summit. An alpha version would signal our progress towards 2.0.0 final, serve as a basis for testing, and give us something to share with a wider audience to solicit feedback on the API, configuration, and module changes. Of course, it would still have to meet ASF release requirements... like licensing and stuff, and it should essentially work (so people can actually run tests), but in an alpha release, we could tolerate flaws we wouldn't in a final release. Ideally, I would have preferred a 2.0.0 final at this point in the year, but I think it needs more testing. Does an alpha release next week seem reasonable to you? Christopher