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 816A691BC for ; Sun, 23 Oct 2011 03:33:15 +0000 (UTC) Received: (qmail 65736 invoked by uid 500); 23 Oct 2011 03:33:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 65707 invoked by uid 500); 23 Oct 2011 03:33:14 -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 65699 invoked by uid 99); 23 Oct 2011 03:33:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 03:33:11 +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 bchesneau@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 03:33:06 +0000 Received: by eyg5 with SMTP id 5so6146231eyg.11 for ; Sat, 22 Oct 2011 20:32:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=971bVxI6Y39IlY90vFKoUbq69KWugJrEadXv/9fgeQY=; b=VwcLPVqbCQdIqiiaovRUtEYHKq5j0oJCMYuFtwtxjPOLv8To5PSopSTSnJRaOfsZHV MezHNs7t+ZWaJyKPTdcAo4TKb93HiYrS3GluQhMASdzbOmwYxNCezbTFKbL4YYR1NhE7 tB4xaR19T60HW3eekf0sbvGhzNfeL03f65ynA= MIME-Version: 1.0 Received: by 10.14.41.155 with SMTP id h27mr2324471eeb.94.1319340764786; Sat, 22 Oct 2011 20:32:44 -0700 (PDT) Received: by 10.14.189.16 with HTTP; Sat, 22 Oct 2011 20:32:44 -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> Date: Sun, 23 Oct 2011 05:32:44 +0200 Message-ID: Subject: Re: Tweaking the release procedure From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Just read about this thread this morning. On Fri, Oct 21, 2011 at 3:18 AM, Noah Slater wrote: > On Fri, Oct 21, 2011 at 2:04 AM, Dustin Sallings wrote: > > v1.7.4.4 =A0 =A0 =A0 =A0Git 1.7.4.4 >> v1.7.4.5 =A0 =A0 =A0 =A0Git 1.7.4.5 >> v1.7.5 =A0 =A0 =A0 =A0 =A0Git 1.7.5 >> v1.7.5-rc0 =A0 =A0 =A0Git 1.7.5-rc0 >> v1.7.5-rc1 =A0 =A0 =A0Git 1.7.5-rc1 >> v1.7.5-rc2 =A0 =A0 =A0Git 1.7.5-rc2 >> v1.7.5-rc3 =A0 =A0 =A0Git 1.7.5-rc3 >> v1.7.5.1 =A0 =A0 =A0 =A0Git 1.7.5.1 >> v1.7.5.2 =A0 =A0 =A0 =A0Git 1.7.5.2 >> v1.7.5.3 =A0 =A0 =A0 =A0Git 1.7.5.3 >> v1.7.5.4 =A0 =A0 =A0 =A0Git 1.7.5.4 >> v1.7.6 =A0 =A0 =A0 =A0 =A0Git 1.7.6 >> v1.7.6-rc0 =A0 =A0 =A0Git 1.7.6-rc0 >> v1.7.6-rc1 =A0 =A0 =A0Git 1.7.6-rc1 >> v1.7.6-rc2 =A0 =A0 =A0Git 1.7.6-rc2 >> v1.7.6-rc3 =A0 =A0 =A0Git 1.7.6-rc3 >> v1.7.6.1 =A0 =A0 =A0 =A0Git 1.7.6.1 >> v1.7.7-rc0 =A0 =A0 =A0Git 1.7.7-rc0 >> >> =A0 =A0 =A0 =A0I very well may be biased, but I don't find that confusin= g. > > > Oh, and by extension, I will give my -1 vote to any system that mixes the= se > two together. The release tag for X.Y.Z should be tied to an official > artefact of the Apache CouchDB project. A tag that doesn't pass the vote > should be deleted. The history is in the X.Y.x release branch. It has no > business cluttering up the tags, and no business confusing users about > whether it has been blessed by the project. > if we where going to something "semantic", then it should probably be rc1.1.x and v1.1.x ... Though I don't like it so much, and it's not really used around. (also just because a buzz around a semver page has been done doesn't mean it should be used). X.X.X for stable version and X.X.X-rcX for release control ? Having tag looking like blah/X.X.X sounds odd . I'm not sure we need to reinvent the wold. About messages in releases and tag I never read them, but couldn't it simply summarize the vote? CHANGES is better to read release notes , also this is the thing that is distributed in the archive. my 2 cents, - beno=EEt http://www.youtube.com/watch?v=3DbrOWtKkHo1M - beno=EEt