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

RE: 1.5.0-rc9 up for signing/testing

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Thu, 5 Jun 2008 01:03:47 +0530

Hi All,

Ran make check * (FS_TYPE=bdb and fsfs)
All tests PASSed.
Ran make svnserveautocheck * (FS_TYPE=bdb and fsfs)
All tests PASSed.
Ran make davautocheck * (FS_TYPE=bdb and fsfs) * (HTTP_LIBRARY=neon).
All tests PASSed.

Ran make davautocheck * (FS_TYPE=bdb and fsfs) * (HTTP_LIBRARY=serf).
Apart from authz_tests.py tests 1 and 12, rest of the other tests have PASSed.

+1 to release as serf is still experimental.

Small hiccups observed:
1. make svnserveautocheck depth_tests-23 has failed over bdb(Cause being not able to remove non-empty directory in our testsuite code), I could not reproduce this again.
2. make davauocheck FS_TYPE=bdb HTTP_LIBRARY merge_tests-4 has failed, I could not reproduce this too again.

My signature for subversion-1.5.0-rc9.tar.bz2

Version: GnuPG v1.2.6 (GNU/Linux)



With regards
Kamesh Jayachandran

-----Original Message-----
From: Hyrum K. Wright [mailto:hyrum_wright_at_mail.utexas.edu]
Sent: Wed 6/4/2008 10:08 AM
To: dev_at_subversion.tigris.org
Subject: 1.5.0-rc9 up for signing/testing
I'm pleased to announce that Subversion 1.5.0-rc9 is up for testing and
signing. The magic revision is r31577. This is another step in our
asymptotic approach to 1.5.0-final.


As usual, 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
unrepairably when they upgrade to 1.5.0 proper. We don't want that kind
of bad publicity, and neither do you.

Received on 2008-06-04 21:34:01 CEST

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.