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

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Wed, 18 Jun 2008 18:49:07 +0530

Hash: SHA1

Hi All,

I built with the following 'configure line'

./configure --prefix=/home/kamesh/svn-1.5.0 --enable-javahl
- --with-jdk=/opt/jdk1.5.0_10 --with-swig=/usr/local/swig-1.3.28
- --with-berkeley-db=/usr --enable-shared --enable-maintainer-mode

I normally used to get couple of warnings in the earlier RCs, while
compiling bundled serf, with this tar ball I did not get any such
warning :).

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 tests have PASSed.

+1 to release as serf is still experimental.

My signature for subversion-1.5.0.tar.bz2

Version: GnuPG v1.2.6 (GNU/Linux)


With regards
Kamesh Jayachandran

Hyrum K. Wright wrote:
> I'm pleased to announce that Subversion 1.5.0 is up for testing and
> signing. The magic revision is r31699. This is the same magic revision
> as rc11, so the differences between the tarballs should be limited to
> svn_version.h.
> http://test.hyrumwright.org/svn/1.5.0/
> 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. Even though
> the code has been tested and signed previously, please test and sign
> this release to ensure code completeness and that I didn't bork the
> packaging somehow.
> 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.
> -Hyrum
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-18 15:19:56 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.