[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

1.6.0 up for testing/signing

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Thu, 19 Mar 2009 15:04:54 -0500

I'm pleased to announce that Subversion 1.6.0 "Hammerhead" is up for
testing and
signing. The magic revision is r36650. You can find the tarballs here:

http://orac.ece.utexas.edu/pub/svn/1.6.0/

This is the proposed final tarball for 1.6.0, and has been created
from the same magic revision as 1.6.0-rc4. If you tested and signed
that tarball, and are comfortable with doing so, you may examine the
diff between 1.6.0 and 1.6.0-rc4 to ensure I didn't do anything
nefarious, and sign the new tarball without testing. I'm shooting for
a morning release tomorrow, so please attempt to sign expeditiously.

[Oh, and PLEASE REVIEW AND UPDATE THE RELEASE NOTES while you're at it.]

You know the drill: signatures from full committers back to me, and
enthusiastic tester feedback is welcome. At this point, this
candidate is not yet blessed for wide release, so please don't make it
available to people not interested in test-driving the new release.

Distro package maintainers, please do NOT include any pre-release
builds, even blessed, into operating system distros. The reasons for
not doing so were very eloquently outlined by Karl in a mail, which is
summarized at the above address.

The quick version is: we don't guarantee compatibility between the pre-
releases and the final release, so if people install the release
candidate, all their repositories and working copies might break
irreparably when they upgrade to 1.6.0 proper. We don't want that
kind of bad publicity, and neither do you.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1357479
Received on 2009-03-19 21:05:13 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.