Return-Path: 
 <release-discuss-return-57-apmail-release-discuss-archive=apache.org@apache.org>
X-Original-To: apmail-release-discuss-archive@minotaur.apache.org
Delivered-To: apmail-release-discuss-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5E99D9BB5
	for <apmail-release-discuss-archive@minotaur.apache.org>;
 Fri,  9 Mar 2012 18:48:13 +0000 (UTC)
Received: (qmail 12108 invoked by uid 500); 9 Mar 2012 18:48:13 -0000
Delivered-To: apmail-release-discuss-archive@apache.org
Received: (qmail 11626 invoked by uid 500); 9 Mar 2012 18:48:12 -0000
Mailing-List: contact release-discuss-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:release-discuss-help@apache.org>
List-Unsubscribe: <mailto:release-discuss-unsubscribe@apache.org>
List-Post: <mailto:release-discuss@apache.org>
List-Id: <release-discuss.apache.org>
Reply-To: release-discuss@apache.org
Delivered-To: mailing list release-discuss@apache.org
Received: (qmail 11610 invoked by uid 99); 9 Mar 2012 18:48:12 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2012 18:48:12 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=10
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.214.178 as permitted sender)
Received: from [209.85.214.178] (HELO mail-tul01m020-f178.google.com)
 (209.85.214.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Mar 2012 18:48:07 +0000
Received: by obbuo19 with SMTP id uo19so3152099obb.23
        for <multiple recipients>; Fri, 09 Mar 2012 10:47:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=29DwfT5q+81LH8+WsQme3Abv+mpVpVlemH9xzH73vYs=;
        b=PvGECsW8vN5LNi1LiOTI7ih9ZOkfVu6OFewa+nDgCOfnAMLF/zHNb/xkQefQZZ6VsC
         NxSKC0C75cmsQqA3hq20Kkvqfd+rfw1Xpgi0Y73zOJQtOuuswTXqrVrW3T1jlBM+YB6P
         l0fjrfRLqCTLouORTPViGXAkzG/tIXEDX8QeS3LNgnVsxI0ulSbtCjf/v5205AnSKGWi
         7PT7ObTaBbnvXXy68EUbdaA13AVwNpVShvO9Qs6LiEe1f54d3zn1mw5CuzojFXBRAx6p
         yl0Sw8XHgRFv3npfAD+T2UNVspNo7GvnHQNWfccYm4T5IFxEkJ9LPe3S3jswCsK2GcWd
         e7xQ==
MIME-Version: 1.0
Received: by 10.60.12.231 with SMTP id b7mr1345887oec.38.1331318866964; Fri,
 09 Mar 2012 10:47:46 -0800 (PST)
Received: by 10.182.85.5 with HTTP; Fri, 9 Mar 2012 10:47:46 -0800 (PST)
In-Reply-To: <20120308134934.GB22646@jack.stsp.name>
References: 
 <CAOGo0VZJJ0Ucd+ZYJVaEUMv-9AgxgQnwQgENDrOAsF5s6za07g@mail.gmail.com>
	<CAOGo0VbKSyCQF=_ETXLzY0VQi14kxjdLbveEfbb4ag938iF-1g@mail.gmail.com>
	<CAOGo0VYUyhTkXU6_DXCj8sZ+-K94yhc916TrHAy61e=t+--3Qw@mail.gmail.com>
	<CABD8fLVc1BcztiuRsxrZ1Hio6P6Zn3Ar4zQ=NyMoarx7jHMT3w@mail.gmail.com>
	<20120303090215.GA28492@daniel3.local>
	<CABD8fLWd1C4pAAGX1ZxzBGJ5R6Lys9qQ9TPb4b13bY7X8bWERw@mail.gmail.com>
	<20120303092845.GB28917@daniel3.local>
	<CAOGo0VY-voQ3ZtYUQTP=LuX-KfQZ+xwpROjxDwyO4nnRFg6szQ@mail.gmail.com>
	<20120303124819.GA31777@daniel3.local>
	<CAOGo0VbJ5fhz2y-1yZn6H-cKO3wFSpboUNM2cjnmtjcy5Sz7NQ@mail.gmail.com>
	<20120308134934.GB22646@jack.stsp.name>
Date: Fri, 9 Mar 2012 18:47:46 +0000
Message-ID: 
 <CAOGo0Va2ijLnopZ0eiiFd+dqoZvsq83PJbndaZNbFDG9r8KYaQ@mail.gmail.com>
Subject: Re: Question on release process - making release public by svn move
From: sebb <sebbaz@gmail.com>
To: Daniel Shahaf <danielsh@apache.org>, Greg Stein <gstein@gmail.com>,
 dev@subversion.apache.org,
	release-discuss@apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

On 8 March 2012 13:49, Stefan Sperling <stsp@elego.de> wrote:
> On Sat, Mar 03, 2012 at 01:03:47PM +0000, sebb wrote:
>> >> >> > 1)
>> >> >> > svnmucc -m logmsg -U https://dist.apache.org/repos/dist/ =A0 \
>> >> >> > =A0 =A0 =A0 =A0mv dev/subversion/subversion-1.7.4.tar.bz2 =A0 =
=A0 =A0 =A0 \
>> >> >> > =A0 =A0 =A0 =A0 =A0 release/subversion/subversion-1.7.4.tar.bz2 =
=A0 =A0 \
>> >> >> > =A0 =A0 =A0 =A0mv dev/subversion/subversion-1.7.4.tar.bz2.asc =
=A0 =A0 \
>> >> >> > =A0 =A0 =A0 =A0 =A0 release/subversion/subversion-1.7.4.tar.bz2.=
asc
>> >> >> >
>
>> > There is also
>> >
>> > 5)
>> > svn co --depth empty https://dist.apache.org/repos/dist/
>> > cd dist
>> > svn up --parents --set-depth infinity dev/subversion release/subversio=
n/
>> > svn mv dev/subversion/* release/subversion/
>>
>> Won't that download every single prior release and all release
>> candidates for subversion?
>
> Yes it will.
>
>> I also asked:
>>
>> How was the following commit acheived?
>>
>> svn log -r397 -v https://dist.apache.org/repos/dist/
>>
>> Whatever was used to generate that commit is good because it shows
>> clearly that the release files were derived from the dev files, for
>> example:
>>
>> =A0 R /release/httpd/CHANGES_2.2 (from /dev/httpd/CHANGES_2.2:396)
>> =A0 A /release/httpd/CHANGES_2.2.21 (from /dev/httpd/CHANGES_2.2.21:396)
>
> I don't know what httpd folks did there.

Neither do I, which is where this all started ...

> For Subversion 1.7.4, I used danielsh's suggestion number 5 simply
> because it is easy to do and I didn't mind downloading the 1.7.3 tarballs=
.

That's not going to be suitable for projects with lots of archives,
e.g. Commons.
And not ideal for projects with very large archive files either.

> I plan to implement suggestion number 1 (using the svnmucc command) in
> subversion's release.py script at
> https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py
> so we can use it for future releases.
>
> Have you found a satisfying solution yet?

No, still waiting for details on how the httpd commits were achieved.