On Thu, Apr 10, 2008 at 8:47 AM, Paul Burba <ptburba_at_gmail.com> wrote:
> 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.
> Votes:
> +1: cmpilato
>
> * 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
> merge target.
> See http://subversion.tigris.org/issues/show_bug.cgi?id=2821#desc22
> Votes:
> +1: pburba(r30464)
> +1: kameshj(r30448)
>
> * r30467
> Fix a bug which can corrupt mergeinfo when filtering self-referential
> mergeinfo.
> See http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=137036.
> Votes:
> +1: pburba
>
> * r30440, r30453, r30462, r30463
> Fix regression. Svnsync doesn't support 1.4 svnserve servers.
> Votes:
> +1: lgo
>
> Shouldn't we push to quickly backport those fixes and roll RC2?
+1
There were also the problems with the Ruby bindings (looks like they
have already been merged). And there was the failing update_test
number 41 when ra_serf was used. Was a fix ever made for that
problem? Personally, I would roll the release anyway, but just
wondering as I did not see it in STATUS.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
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:55:35 CEST