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 EEA699A6D for ; Fri, 21 Oct 2011 21:55:20 +0000 (UTC) Received: (qmail 97504 invoked by uid 500); 21 Oct 2011 21:55:20 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 97470 invoked by uid 500); 21 Oct 2011 21:55:20 -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 97462 invoked by uid 99); 21 Oct 2011 21:55:20 -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 21:55:20 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of dustin@spy.net does not designate 69.230.8.158 as permitted sender) Received: from [69.230.8.158] (HELO eve.west.spy.net) (69.230.8.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Oct 2011 21:55:14 +0000 Received: by eve.west.spy.net (Postfix, from userid 1001) id C6CAC14BDE6; Fri, 21 Oct 2011 14:54:51 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eve.west.spy.net X-Spam-Level: Received: from dhcp-113.west.spy.net (dhcp-113.west.spy.net [192.168.1.113]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by eve.west.spy.net (Postfix) with ESMTPSA id B4C0D14BDE2 for ; Fri, 21 Oct 2011 14:54:26 -0700 (PDT) From: Dustin Sallings Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_3A44677E-FF78-4052-A7B3-2D893D110F6A" Subject: Re: Tweaking the release procedure Date: Fri, 21 Oct 2011 14:54:25 -0700 In-Reply-To: To: dev@couchdb.apache.org 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> Message-Id: X-Mailer: Apple Mail (2.1251.1) X-Old-Spam-Status: No, score=-1.5 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE, RP_MATCHES_RCVD autolearn=ham version=3.3.2 --Apple-Mail=_3A44677E-FF78-4052-A7B3-2D893D110F6A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On Oct 21, 2011, at 2:23 PM, Robert Newson wrote: > In all vote emails, we include the commit id that the release > artifacts were built from, but create no tag at all. >=20 > When the release passes the votes, we create the tag, with its final > name, against that commit id, and push it at the same time we upload > the artifact to the mirrors. >=20 > To obviate any concern about stale 1.1.1 tags in downstream repos, we > could, for this release only, add a 1.1.1-final tag as an unambiguous > tag, but only *after* the release is official. >=20 > Stated another way; we make each tag exactly once, and refer to the > build by its commit id until then. Since a commit id in git dictates > the precise state of the entire tree this is safe. Makes sense to me. "git describe" instead of plain commit IDs = is pretty good for this as well since they'll be slightly easier to talk = about, but same effect. --=20 dustin sallings --Apple-Mail=_3A44677E-FF78-4052-A7B3-2D893D110F6A--