> -----Original Message-----
> From: Stefan Sperling [mailto:stsp_at_elego.de]
> Sent: zondag 5 mei 2013 15:03
> To: Ben Reser
> Cc: Subversion Development
> Subject: Re: 1.8.0-rc1 up for testing/signing
>
> On Fri, May 03, 2013 at 05:34:49PM -0700, Ben Reser wrote:
> > Here it is: the first Release Candidate for Subversion 1.8.0. You can
> > fetch the proposed tarballs from here:
> > https://dist.apache.org/repos/dist/dev/subversion
> >
> > The magic rev is r1478983
> >
> > This is a release candidate, meaning if all goes well it (or something
> > very much like it) will become the final release.
>
> The CHANGES file in the tarball is incomplete. At the very least, it
> lacks some cleanup and a projected release date. Do we really want to
> issue the 1.8.0 release with an incomplete CHANGES file?
>
> Should we update the swig dependency to swig-2.0.9? I noticed that the
> release.py script is still using 2.0.4, which was also used for 1.7.0.
The standard procedure is that we create a new tarball right before the
final .0 release, at the end of the grace period. (see HACKING)
The code might be identical, but at least the svn_version.h, localization
and documentation won't be. Looking back at 1.5, 1.6 and 1.7 there might be
a few more release candidates based on initial real-world testing...
But I'm quite positive that we won't need as many candidates as the last few
times. But let's discuss that after the final release.
But in the past we did our usual testing and signing rounds for release
candidates too... I don't see that activity now?
Bert
Received on 2013-05-05 15:47:32 CEST