Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-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 D7C219F36 for ; Fri, 21 Oct 2011 03:58:42 +0000 (UTC) Received: (qmail 32386 invoked by uid 500); 21 Oct 2011 03:58:41 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 32109 invoked by uid 500); 21 Oct 2011 03:58:40 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 32100 invoked by uid 99); 21 Oct 2011 03:58:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 03:58:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vx0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 03:58:33 +0000 Received: by vcbfo11 with SMTP id fo11so4471721vcb.11 for ; Thu, 20 Oct 2011 20:58:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=0b8dfwg9Y6dg+b6tfcH2bub1XIFCEUgKxGrl4AsElD4=; b=BiTGvBnZPIso8eSwRTXQfhCbJqrELJrYuIzrMA/mFHmt0HHEM7lXL/6Jg0RvOyYgiH jCVCyokgf95xEBsdxOWWGH8v5lJEjQI6NkSoN3hb8Wt5lFSZFeA0TPq/0EXYUoiYT8Ju bETdvHw/jQcsIhHfFIzOlWLKhUmx5fS6pNME4= Received: by 10.52.69.115 with SMTP id d19mr12789257vdu.71.1319169492060; Thu, 20 Oct 2011 20:58:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.167.71 with HTTP; Thu, 20 Oct 2011 20:57:32 -0700 (PDT) In-Reply-To: References: <6BC9C06A-D317-409F-83E8-F898CAB3A617@spy.net> <6B64ED84-544F-4C84-9DD4-D794AD025380@spy.net> <82F3E1E5-A9C7-4EC7-BEBF-E4BAD753AF85@gmail.com> <4FD791CC-15A9-4FE9-97B6-76D1B2BD850C@spy.net> From: Paul Davis Date: Thu, 20 Oct 2011 22:57:32 -0500 Message-ID: Subject: Re: Tweaking the release procedure To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Oct 20, 2011 at 8:23 PM, Noah Slater wrote: > On Fri, Oct 21, 2011 at 2:04 AM, Dustin Sallings wrote: > > In the above example, if someone downloaded and is currently running >> 1.1.1-rc1 and he looks at the list of tags and sees v1.1.1, v1.1.1-rc1 a= nd >> v1.1.1-rc2, why would be confused? =A0More importantly, you released tha= t, so >> why would you not want the user to be able to see whether any changes >> between 1.1.1-rc1 and 1.1.1 final affect his deployment? > > > If someone has downloaded and is running an artefact from a botched relea= se > vote, our release procedure has failed us catastrophically. Nobody should > EVER be running these as-of-yet-not-approved release artefacts. Except fo= r > testing and voting, obviously. Hence, the only reason you'd want to see w= hat > the changes were between 1.1.1-rc1 and 1.1.1 would be for testing a secon= d > round of voting. Perhaps we should eschew the "release candidate" > nomenclature if it is causing these problems? I am worried that we might = be > sending the wrong message to our users who expect this terminology to mea= n > something else entirely. Oh, and Sorry about replying in > a piecemeal fashion! > Piecemeal helps us find our way back. http://en.wikipedia.org/wiki/Hansel_and_Gretel