From dev-return-18760-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Fri Oct 21 20:10:13 2011 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 B840090FE for ; Fri, 21 Oct 2011 20:10:13 +0000 (UTC) Received: (qmail 21495 invoked by uid 500); 21 Oct 2011 20:10:13 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 21458 invoked by uid 500); 21 Oct 2011 20:10:13 -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 21449 invoked by uid 99); 21 Oct 2011 20:10:13 -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 20:10:13 +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 20:10:07 +0000 Received: by vcbfo11 with SMTP id fo11so5397362vcb.11 for ; Fri, 21 Oct 2011 13:09:47 -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=4yO0MqAO4lgMv6Sk45tW0MaK4P38ozud8iQKpJ1kvmE=; b=siz65/SAWOBWy2DuICZQccA1lzJVXyScMweXgRH7VdoZWy6rZ7Ghj2UpDHN/50ITXG mYYKDb2TV/BTAci1o5PADRHRd6R5l3ypTPheFy9D5Vjb4xi0LLMigSKMZVY4Vi0p+8mF 5t9cWSP6RL/x8XgYTCjcQGNnTrzzRFpDB6Hmk= Received: by 10.52.34.78 with SMTP id x14mr15392531vdi.122.1319227787101; Fri, 21 Oct 2011 13:09:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.167.71 with HTTP; Fri, 21 Oct 2011 13:09:07 -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> <166A20A5-399A-4965-ADB9-B4E377D0F41A@spy.net> From: Paul Davis Date: Fri, 21 Oct 2011 15:09:07 -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 Fri, Oct 21, 2011 at 2:42 PM, Dustin Sallings wrote: > > On Oct 21, 2011, at 11:25 AM, Robert Newson wrote: > >> /tmp/bar $ git pull --tags >> remote: Counting objects: 4, done. >> remote: Compressing objects: 100% (2/2), done. >> remote: Total 3 (delta 0), reused 0 (delta 0) >> Unpacking objects: 100% (3/3), done. >> From /tmp/foo >> - [tag update] =A0 =A0 =A01.0 =A0 =A0 =A0 =A0-> 1.0 >> Fetching tags only, you probably meant: >> =A0git fetch --tags >> >> The 1.0 tag was correctly updated. > > > =A0 =A0 =A0 =A0You aren't disagreeing with the thing I'm most concerned, = but the thing I'm second-to-most concerned about but directly brought up. > > =A0 =A0 =A0 =A0I pointed out that you can't *remove* tags, since that's w= hat's required for a renaming strategy. =A0Here you're just showing that if= every user everywhere who has a clone of the official repo issues a non-de= fault update command before looking at tags, then there's no problem. =A0I = think this might be less reasonable than it sounds. I think our wires were crossed a bit. The rename isn't really a rename directly. Once a release is made, we just copy the final vote tag to a new tag that is prefixed/suffixed/something to indicate "this is the tag that corresponds to what's in the dist directory." Removing tags would occur after a final vote passed and would only be a minor "maybe get rid of cruft to avoid confusion" step. > > =A0 =A0 =A0 =A0For example: =A0Let's say I'm doing an automated build for= my OS distribution from the 1.0 tag and have shipped stuff out to my custo= mers. =A0How will you know that there was no failure in my two tiers of git= repos that caused my build to miss the update to your 1.0 tag between the = time that you issued the first one, announced the second one, I did an upda= te from a mirror during an upstream outage and see the 1.0 tag and ship it = and then find a bug? =A0Which 1.0 did I ship? > Right, this is the current state of affairs we've been dealing with using SVN and what we're looking to fix. > -- > dustin sallings > > > >