On Tue, 16 May 2006, Stefan Küng wrote:
> Peter N. Lundblad wrote:
> >Stefan Küng writes:
> > > Ben Collins-Sussman wrote:
> > > > On 5/16/06, Garrett Rooney <email@example.com> wrote:
> > > >> So we branched 1.4.x a little while back, are there any plans for
> > > >> actually tagging a release candidate off of it? If so, when? I'd
> > > >> like to roll a version of it up on svn.collab.net for testing
> > purposes
> > > >> (specifically to try out the new bdb 4.4 stuff), but historically we
> > > >> haven't done that until there's actually been a release candidate
> > > >> tarball.
> > > >
> > > > Yeah, I thought that our typical process was to release an rc1 tarball
> > > > for testing right after branching...?
> > >
> > > Not sure if this should hold up an RC, but I think this one is pretty
> > > serious and should be fixed soon (it may not affect the CL client that
> > > much, but it does TSVN a *lot* because we rely on this to work).
> > > http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=115783
> > >
> >(This is svn log path@BASE failing, BTW.)
> >If it is a regression, it should definitely block the release. Would you
> >filing an issue with the 1.4 milestone so it doesn't get forgotten?
> I think it is a regression.
> Filed as issue 2550:
> btw: the issuetracker needs to have an "1.4.x" version tag.
This regression has been fixed on the trunk and 1.4.x branch.
Committers, there are still a number of items in STATUS that could use
your votes. We're really close to a RC (famous last words ;).
Received on Thu May 18 03:29:41 2006
- application/pgp-signature attachment: stored