www-release-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: Question on release process - making release public by svn move
Date Thu, 08 Mar 2012 13:49:34 GMT
On Sat, Mar 03, 2012 at 01:03:47PM +0000, sebb wrote:
> >> >> > 1)
> >> >> > svnmucc -m logmsg -U https://dist.apache.org/repos/dist/   \
> >> >> >        mv dev/subversion/subversion-1.7.4.tar.bz2      
  \
> >> >> >           release/subversion/subversion-1.7.4.tar.bz2  
  \
> >> >> >        mv dev/subversion/subversion-1.7.4.tar.bz2.asc    
\
> >> >> >           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/subversion/
> > 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:
> 
>   R /release/httpd/CHANGES_2.2 (from /dev/httpd/CHANGES_2.2:396)
>   A /release/httpd/CHANGES_2.2.21 (from /dev/httpd/CHANGES_2.2.21:396)

I don't know what httpd folks did there.

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.

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?

Mime
View raw message