[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-rc11 up for signing/testing

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Wed, 11 Jun 2008 23:15:36 +0530

Hi All,

Got some tests failing when ran through the testsuite with all testcases,
when later ran them individually they succeeded, it should be our testsuite
issue which I can not consistently reproduce.

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

+1 to release as serf is still experimental.

My signature for subversion-1.5.0-rc11.tar.bz2(Signed from other box where my
digital fingerprint could be different, I am not sure how to use the same
fingerprint across different boxes.

Version: GnuPG v1.4.6 (GNU/Linux)


With regards
Kamesh Jayachandran

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


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
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-11 19:45:55 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.