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.
