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 8DEAE113BF for ; Thu, 19 Jun 2014 19:13:39 +0000 (UTC) Received: (qmail 22055 invoked by uid 500); 19 Jun 2014 19:13:39 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 22014 invoked by uid 500); 19 Jun 2014 19:13:39 -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 21993 invoked by uid 99); 19 Jun 2014 19:13:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2014 19:13:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of josh.elser@gmail.com designates 209.85.160.53 as permitted sender) Received: from [209.85.160.53] (HELO mail-pb0-f53.google.com) (209.85.160.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2014 19:13:34 +0000 Received: by mail-pb0-f53.google.com with SMTP id uo5so2218348pbc.40 for ; Thu, 19 Jun 2014 12:13:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=xRgxkTbLUyxQnvMsw8zsS6MTRKXORQG5fYQdvYTSJ0c=; b=jAItswkizPFepEYs98vEwNTH6Zj64oa3zVlLpEFOGQVQPftyxo7ZvP/k0ua57G0yVe PCZljpgMo+oLhFA/H3gR+gyQ6JxS+gDOxMiKavPNZPQB8cfhk21xjIcoltXN6TkqL/rD B+USiJx1ApGQM0PeheIaiAYdBjOZw38389kpbgXQtsKI2qL8kzfsjPAZ8NsXBV62JVU4 XP+z/dPHE4VX+PiqFcnb5UEZsiP7hE6spcv6GohVb8ppSuEWYaCDkul2dIYl+6aLD0eu 464wbEYCl8PKgJLUB69rrElEjMAmakmQtF6etQh1QQti/B5sGAD/DX+/D1B3VLW4/VPD HQ1g== X-Received: by 10.68.237.133 with SMTP id vc5mr8197302pbc.92.1403205189570; Thu, 19 Jun 2014 12:13:09 -0700 (PDT) Received: from HW10447.local ([192.175.27.2]) by mx.google.com with ESMTPSA id ek2sm9836043pbd.30.2014.06.19.12.13.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 12:13:08 -0700 (PDT) Message-ID: <53A33643.7000603@gmail.com> Date: Thu, 19 Jun 2014 12:13:07 -0700 From: Josh Elser User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev Subject: Reduced testing burden for bug-fix releases Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org As we're starting to consider 1.5.2 and 1.6.1 coming out in the near future, I want to revisit a discussion[1] I started at the end of April regarding the "testing burden" that is currently set forth in our release document[2]. What I'm proposing is to modify the language of the release document to be explicit about the amount of testing needed. For bug-fix, "minor" releases (e.g. 1.5.2 and 1.6.1), the 7 days of testing using continuous ingest and randomwalk (with and without agitation) will be clearly defined as "may" instead of "should" or "must" language. If the resources are available, it is recommended that some longer, multi-process/node test is run against the release candidate; however, it is not required and should not prevent us from making the minor release. I will also include language that strongly recommends that the changes included in the "minor" release be vetted/reviewed as a way to mitigate the risk of shipping new regressions. I am not recommending that the language be changed for "major" releases (e.g. 1.7.0 and 2.0.0) as these releases still imply significant new features or internal changes. Unless someone informs me otherwise, I will treat this as a normal lazy-consensus approval. Assuming we move closer to "proper" semantic versioning for 2.0.0, I believe these updated guidelines will change again. I do however think there is merit in making this change now so that we can get the good bugs that we've fixed out to our users. Let me know what you think. I will wait, at least, the prescribed three days before changing any thing. - Josh [1] http://mail-archives.apache.org/mod_mbox/accumulo-dev/201404.mbox/%3C535931A7.30605%40gmail.com%3E [2] http://accumulo.apache.org/governance/releasing.html