You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Garrett Rooney <ro...@electricjellyfish.net> on 2006/06/18 14:17:41 UTC
1.4.0 Release Candidate Status?
Hey, so it occurs to me that we still haven't publicly released the
first RC of 1.4.0. What's the status on that?
I know there are certainly some showstoppers for 1.4.0 final (the BDB
stuff Branko is working on, if nothing else), but is there anything
out there that's keeping us from getting some more eyes on the rest of
this code?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.4.0 Release Candidate Status?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 6/18/06, Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp> wrote:
> It seems RC1 is somewhat outdated anymore; some important improvement
> such as changes related to the blame issue has got in the 1.4.0 release
> branch after the tarball for RC1 was created. So, I propose to create
> a tarball RC2 instead of releasing RC1 publicly, if we can check and
> attach signatures soon.
>
> As we can see in www/project_status.html, we had publicly released only
> RC4 and RC7 before 1.3.0 although we had had tarballs (and tags) for other
> release candidates.
There are certainly a number of bug fixes (and there will be more
before release), but either way I'd just like us to get moving in a
direction here. I don't particularly care if that direction is
releasing the existing tarball or rolling a new one, but we should be
doing something other than just sitting around.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.4.0 Release Candidate Status?
Posted by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>.
Hi,
David Anderson wrote:
> > Hey, so it occurs to me that we still haven't publicly released the
> > first RC of 1.4.0. What's the status on that?
>
> It is my fault that things have been lagging, as I've been fairly busy
> away from svn. Thanks for the kick!
>
> So, we still need 1 win32 signature to release. For the rest, there
> is sufficient coverage.
>
> Ben, can you get a build going? Branko and djheap have both signed, so
> that leaves you :-)
Some comments from a partial committer. :-)
It seems RC1 is somewhat outdated anymore; some important improvement
such as changes related to the blame issue has got in the 1.4.0 release
branch after the tarball for RC1 was created. So, I propose to create
a tarball RC2 instead of releasing RC1 publicly, if we can check and
attach signatures soon.
As we can see in www/project_status.html, we had publicly released only
RC4 and RC7 before 1.3.0 although we had had tarballs (and tags) for other
release candidates.
Thanks,
-nori
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.4.0 Release Candidate Status?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 6/19/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> On Sun, Jun 18, 2006 at 08:08:57PM +0200, David Anderson wrote:
> > - BDB and svnserve bug that causes commits to silently rollback when
> > in forking mode
> >
>
> Only with repositories created with --bdb-txn-nosync, I think.
Correct.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.4.0 Release Candidate Status?
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Sun, Jun 18, 2006 at 08:08:57PM +0200, David Anderson wrote:
> - BDB and svnserve bug that causes commits to silently rollback when
> in forking mode
>
Only with repositories created with --bdb-txn-nosync, I think.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.4.0 Release Candidate Status?
Posted by David Anderson <da...@calixo.net>.
* Garrett Rooney <ro...@electricjellyfish.net> [2006-06-18 10:17:41]:
> Hey, so it occurs to me that we still haven't publicly released the
> first RC of 1.4.0. What's the status on that?
It is my fault that things have been lagging, as I've been fairly busy
away from svn. Thanks for the kick!
So, we still need 1 win32 signature to release. For the rest, there
is sufficient coverage.
Ben, can you get a build going? Branko and djheap have both signed, so
that leaves you :-)
> I know there are certainly some showstoppers for 1.4.0 final (the BDB
> stuff Branko is working on, if nothing else), but is there anything
> out there that's keeping us from getting some more eyes on the rest of
> this code?
On that subject, what issues should be reported to users when rc1 is
published? So far, I have:
- Warning, wc format bump
- BDB and svnserve bug that causes commits to silently rollback when
in forking mode
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org