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 3987811B87 for ; Fri, 19 Sep 2014 05:03:16 +0000 (UTC) Received: (qmail 15680 invoked by uid 500); 19 Sep 2014 05:03:15 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 15643 invoked by uid 500); 19 Sep 2014 05:03:15 -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 15626 invoked by uid 99); 19 Sep 2014 05:03:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 05:03:15 +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 (nike.apache.org: domain of mdrob@cloudera.com designates 209.85.219.49 as permitted sender) Received: from [209.85.219.49] (HELO mail-oa0-f49.google.com) (209.85.219.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Sep 2014 05:02:50 +0000 Received: by mail-oa0-f49.google.com with SMTP id jd19so1316382oac.8 for ; Thu, 18 Sep 2014 22:02:48 -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:from:date :message-id:subject:to:content-type; bh=suCA+YGSAB13gS118o7pUAv9W0iy4ulwDzneBntFhH8=; b=Adm7iH2mk0j0cJEkweXa+91aymDlGegwTvVnuKD7gLR6biHAavHWyp3QVfyTY2xNxh f92Wea2ax0148RthhJ2L0aTq5xgZfYhfspkF2wAueeZgKG9vAHO0YFOg+/XH5BWJohv9 HY+VMS0U5tJnCUTlkw6+HLWn4wV0ch/cRtR4WCBp9BqmgmthY0HinYidgqFT0wglNcJ+ 8H4xyHpxFTE7TXnWXUDvY3G7+1FKXlaLOfh4yxIMDy//bbhWemEq0WtlVJv2i1jPpQz8 7k15/dQ7jxqKnzWgg1PWHCfTsGVIWn6pP9gBfR6epm/PkCvW1TON1QALI4F+j+W1pEHk DdEw== X-Gm-Message-State: ALoCoQn77y4EbxIYlohs+gnrUTJv7mPwDfbEyznvWgnUchwdg1HbpjRCRhX1sNRaPFLBHR7y8f5j X-Received: by 10.182.133.104 with SMTP id pb8mr5159831obb.37.1411102968835; Thu, 18 Sep 2014 22:02:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.123.12 with HTTP; Thu, 18 Sep 2014 22:02:28 -0700 (PDT) In-Reply-To: References: <541712A2.30204@gmail.com> <541B9305.7030506@gmail.com> From: Mike Drob Date: Thu, 18 Sep 2014 22:02:28 -0700 Message-ID: Subject: Re: [VOTE] Apache Accumulo 1.5.2 RC1 To: Accumulo Dev List Content-Type: multipart/alternative; boundary=e89a8ff1ce2233017805036403bb X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1ce2233017805036403bb Content-Type: text/plain; charset=UTF-8 Did we bundle 1.5.1/1.6.0? If not, they were fairly close together, I think. Historically, we have not done a great job of distinguishing our release lines, so that has led to confusion. Maybe I'm on the path to talking myself out of a combined announcement here. On Thu, Sep 18, 2014 at 9:57 PM, William Slacum < wilhelm.von.cloud@accumulo.net> wrote: > Not to be a total jerk, but what's unclear about 1.5 < 1.6? Lots of > projects have multiple release lines and it's not an issue. > > On Fri, Sep 19, 2014 at 12:18 AM, Mike Drob wrote: > > > +1 to combining. I've already had questions about upgrading to "this > latest > > release" from somebody currently on the 1.6 line. Our release narrative > is > > not clear and we should not muddle the waters. > > > > On Thu, Sep 18, 2014 at 7:27 PM, Christopher > wrote: > > > > > Should we wait to do a release announcement until 1.6.1, so we can > batch > > > the two? > > > > > > My main concern here is that I don't want to encourage new 1.5.x > adoption > > > when we have 1.6.x, and having two announcements could be confusing to > > new > > > users who aren't sure which version to start using. We could issue an > > > announcement that primarily mentions 1.6.1, and also mentions 1.5.2 > > second. > > > That way, people will see 1.6.x as the stable/focus release, but will > > still > > > inform 1.5.x users of updates. > > > > > > > > > -- > > > Christopher L Tubbs II > > > http://gravatar.com/ctubbsii > > > > > > On Thu, Sep 18, 2014 at 10:20 PM, Josh Elser > > wrote: > > > > > > > Vote passes with 3 +1's and nothing else. Huge thank you to those who > > > made > > > > the time to participate. > > > > > > > > I'll finish up the rest of the release work tonight. > > > > > > > > On 9/15/14, 12:24 PM, Josh Elser wrote: > > > > > > > >> Devs, > > > >> > > > >> Please consider the following candidate for Apache Accumulo 1.5.2 > > > >> > > > >> Tag: 1.5.2rc1 > > > >> SHA1: 039a2c28bdd474805f34ee33f138b009edda6c4c > > > >> Staging Repository: > > > >> https://repository.apache.org/content/repositories/ > > > >> orgapacheaccumulo-1014/ > > > >> > > > >> Source tarball: > > > >> http://repository.apache.org/content/repositories/ > > > >> orgapacheaccumulo-1014/org/apache/accumulo/accumulo/1.5. > > > >> 2/accumulo-1.5.2-src.tar.gz > > > >> > > > >> Binary tarball: > > > >> http://repository.apache.org/content/repositories/ > > > >> orgapacheaccumulo-1014/org/apache/accumulo/accumulo/1.5. > > > >> 2/accumulo-1.5.2-bin.tar.gz > > > >> > > > >> (Append ".sha1", ".md5" or ".asc" to download the signature/hash > for a > > > >> given artifact.) > > > >> > > > >> Signing keys available at: > https://www.apache.org/dist/accumulo/KEYS > > > >> > > > >> Over 1.5.1, we have 109 issues resolved > > > >> https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a= > > > >> blob;f=CHANGES;h=c2892d6e9b1c6c9b96b2a58fc901a76363ece8b0;hb= > > > >> 039a2c28bdd474805f34ee33f138b009edda6c4c > > > >> > > > >> > > > >> Testing: all unit and functional tests are passing and ingested 1B > > > >> entries using CI w/ agitation over rc0. > > > >> > > > >> Vote will be open until Friday, August 19th 12:00AM UTC (8/18 8:00PM > > ET, > > > >> 8/18 5:00PM PT) > > > >> > > > >> - Josh > > > >> > > > > > > > > > > --e89a8ff1ce2233017805036403bb--