On Mon, Apr 7, 2008 at 7:16 PM, Hyrum K. Wright
> Good afternoon,
> I'm pleased to announce that Subversion 1.5.0-rc1 is up for testing and
> signing. The magic revision is r30419.
> 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 to 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
> canditate, 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.
Given that we have found several serious problems with RC1, in
particular these items in STATUS:
* r30455, r30460
Use 1:PEG_REV instead of 1:HEAD as the default operative revision
range when a peg revision is supplied to a single-URL merge command.
* r30448, r30464
r30448: XFail Testcase to showcase the bug.
r30464: Fix reopened issue #2821. Fixes a bug where repeat merges can
easily occur when merging into subtrees with differing mergeinfo from the
Fix a bug which can corrupt mergeinfo when filtering self-referential
* r30440, r30453, r30462, r30463
Fix regression. Svnsync doesn't support 1.4 svnserve servers.
Shouldn't we push to quickly backport those fixes and roll RC2?
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-10 14:47:47 CEST