You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Malcolm Rowe <ma...@farside.org.uk> on 2006/03/05 20:45:47 UTC
The time for 1.3.1 is nigh
So we released 1.3.0 just over two months ago, and I think it's probably
about time for 1.3.1.
We've taken some fairly important fixes (see below), but the state of
things seems pretty much unchanged since djames' similar request at the
end of January - we're still waiting for the BDB 4.4 fixes. These aren't
yet complete on trunk, and - no offence to brane - I don't think we
want to release them directly into a stable release branch without the
benefit of exposure on trunk first.
So, could I propose the end of next week as a target for merging the
remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
Regards,
Malcolm
Changes in 1.3.x since 1.3.0 (mostly purloined from djames' message at
http://svn.haxx.se/dev/archive-2006-01/0924.shtml - including approved
changes in STATUS):
Core libraries:
- Fix crashes on mixed-case https:// URLs (r18042)
- Fix mv --force segfaults on unversioned files (r17242, r17243)
- Fix crash in svn status -u when an ignored directory is also in the
repository (r18291)
- Fix crash with diff and non-recursive checkout (r17231, r18539, r18541)
- Add missing error-handling checks, one of which was responsible for
server-side segfaults (r18249, r18196)
- Fix verbose list when used with peg revisions over ra_dav (r17485, r18027)
- Make mod_dav_svn log all the errors in a given chain, rather than
just the first one
- Don't block waiting for background jobs of hook scripts (r18146)
- Set svn:date at the end of each commit, not the start (FSFS) (r18078)
- Strip peg revisions from the default name of checkout directories (r18416)
- Support Neon 0.25.5 (r18215)
Client-side:
- Fix a regression which caused 'svn ci -m path_name' to no longer
require --force-log (r17956)
- Updates to svnmerge.py (various)
Ruby/SWIG bindings:
- Fix memory leaks (r17795, r17811)
- Fix character-set conversion bugs (r17726, r17925)
- Fix garbage collection segfaults (r17627)
- Fix the Ruby bindings compile error with SWIG 1.3.24 (r18456, r18458)
Python/SWIG bindings:
- Fix memory leaks (r18230)
- Fix assertion errors (r17792)
- Fix linking errors on Solaris 10 (r17910)
plus other miscellaneous changes (compilation: r18054, r18055, r18065;
packaging: r17829, r17831; default config file clarifications: r18247,
r18250).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Ivan Zhakov <ch...@gmail.com>.
On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> So we released 1.3.0 just over two months ago, and I think it's probably
> about time for 1.3.1.
>
> We've taken some fairly important fixes (see below), but the state of
> things seems pretty much unchanged since djames' similar request at the
> end of January - we're still waiting for the BDB 4.4 fixes. These aren't
> yet complete on trunk, and - no offence to brane - I don't think we
> want to release them directly into a stable release branch without the
> benefit of exposure on trunk first.
>
> So, could I propose the end of next week as a target for merging the
> remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
+1 for release 1.3.1 on the end of next week.
--
Ivan Zhakov
Re: The time for 1.3.1 is nigh
Posted by kf...@collab.net.
Branko Čibej <br...@xbc.nu> writes:
> Peter N. Lundblad wrote:
> > Garrett Rooney writes:
> > > On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> > > > So, could I propose the end of next week as a target for merging the
> > > > remaining changes in STATUS, for a release of 1.3.1 shortly
> > > > thereafter?
> > > > And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
> > > > +1
> > > And you can take my recent commit activity (which actually *was*
> > coinsidental:-) as a +1 as well. There is nothing stopping us from
> > doing 1.3.2 quickly, should the BDB stuff be ready soon after 1.3.1.
+1 here too, and also to what Peter said about a fast 1.3.2 when we're
ready.
> I agree. I'm sorry the BDB bugfix is late, it's all due to an
> unfortunate combination of circumstances.
Sleep & health first, BDB bugfix second, is all I have to say.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Branko Čibej <br...@xbc.nu>.
Peter N. Lundblad wrote:
> Garrett Rooney writes:
> > On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> > > So, could I propose the end of next week as a target for merging the
> > > remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
> > > And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
> >
> > +1
> >
>
> And you can take my recent commit activity (which actually *was*
> coinsidental:-) as a +1 as well. There is nothing stopping us from
> doing 1.3.2 quickly, should the BDB stuff be ready soon after 1.3.1.
>
I agree. I'm sorry the BDB bugfix is late, it's all due to an
unfortunate combination of circumstances.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
Garrett Rooney writes:
> On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> > So, could I propose the end of next week as a target for merging the
> > remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
> > And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
>
> +1
>
And you can take my recent commit activity (which actually *was*
coinsidental:-) as a +1 as well. There is nothing stopping us from
doing 1.3.2 quickly, should the BDB stuff be ready soon after 1.3.1.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> So we released 1.3.0 just over two months ago, and I think it's probably
> about time for 1.3.1.
>
> We've taken some fairly important fixes (see below), but the state of
> things seems pretty much unchanged since djames' similar request at the
> end of January - we're still waiting for the BDB 4.4 fixes. These aren't
> yet complete on trunk, and - no offence to brane - I don't think we
> want to release them directly into a stable release branch without the
> benefit of exposure on trunk first.
>
> So, could I propose the end of next week as a target for merging the
> remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
> And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
+1
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 3/5/06, Malcolm Rowe <ma...@farside.org.uk> wrote:
> So, could I propose the end of next week as a target for merging the
> remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
> And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
If Dave Anderson isn't available, I'll volunteer to RM once all of the
changes are merged into 1.3.x. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
Manuzhai writes:
> > Python/SWIG bindings:
> > - Fix memory leaks (r18230)
> > - Fix assertion errors (r17792)
> > - Fix linking errors on Solaris 10 (r17910)
>
> Can we have r18721 ported as well? It fixed a nasty bug in Trac for me,
> and it'd be nice if that could get fixed in 1.3.1.
>
That's already in STATUS. See
http://svn.collab.net/repos/svn/branches/1.3.x/STATUS
(It needs one more vote to get approved.)
Best,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Manuzhai <ma...@supaari.manuzhai.nl>.
> Python/SWIG bindings:
> - Fix memory leaks (r18230)
> - Fix assertion errors (r17792)
> - Fix linking errors on Solaris 10 (r17910)
Can we have r18721 ported as well? It fixed a nasty bug in Trac for me,
and it'd be nice if that could get fixed in 1.3.1.
Regards,
Manuzhai
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by David Anderson <da...@calixo.net>.
* Malcolm Rowe <ma...@farside.org.uk> [2006-03-13 11:40:33]:
> If we wanted to, I suppose we could split out the SWIG 1.3.26/27 support
> from the 17280 group and merge that, leaving the 1.3.28 support unmerged
> for now. But I doubt it's worth it - I've not heard any complaints
> about the fact that 1.3.0 only supported SWIG 1.3.24/25.
>
> Release early, release often.
As I've said on IRC, I've started rolling. I've reinstalled my system
since the last time, so it might take a few iterations to get
right. I've frozen at r18866.
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Mon, Mar 13, 2006 at 12:09:14PM +0100, Peter N. Lundblad wrote:
> +1. The failed Ruby test on breakage@ from me is just because I installed
> swig 1.3.28 yesterday for testing, so nothing to worry about since we don't
> officially support 1.3.28 in 1.3.1 (as it seems now).
>
If we wanted to, I suppose we could split out the SWIG 1.3.26/27 support
from the 17280 group and merge that, leaving the 1.3.28 support unmerged
for now. But I doubt it's worth it - I've not heard any complaints
about the fact that 1.3.0 only supported SWIG 1.3.24/25.
Release early, release often.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by "Peter N. Lundblad" <pe...@famlundblad.se>.
Malcolm Rowe writes:
> On Fri, Mar 10, 2006 at 01:53:16PM +0100, David Anderson wrote:
> > So, if you are satisfied with the state of the release branch, I can
> > get an RC out the door this weekend. If not, I can help review stuff,
> > or if you need more time to finalize things, just ping me when you're
> > ready.
> >
>
> Unless anyone disagrees, I think we're now ready to roll 1.3.1.
>
+1. The failed Ruby test on breakage@ from me is just because I installed
swig 1.3.28 yesterday for testing, so nothing to worry about since we don't
officially support 1.3.28 in 1.3.1 (as it seems now).
What worries me a little is that we don't seem to have nightly 1.3.x
tests on windows, but we'll catch such problem in the signing process
anyway. But it would be really nice if someone more interested in
Windows than me could set up nightly builds and tests for 1.3.x as
well.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Fri, Mar 10, 2006 at 01:53:16PM +0100, David Anderson wrote:
> So, if you are satisfied with the state of the release branch, I can
> get an RC out the door this weekend. If not, I can help review stuff,
> or if you need more time to finalize things, just ping me when you're
> ready.
>
Unless anyone disagrees, I think we're now ready to roll 1.3.1.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by "C. Michael Pilato" <cm...@collab.net>.
David Anderson wrote:
> When I volunteered for RM, it was with the understanding that I'd
> continue unless stated otherwise.
Yay!
> So, if you are satisfied with the state of the release branch, I can
> get an RC out the door this weekend. If not, I can help review stuff,
> or if you need more time to finalize things, just ping me when you're
> ready.
Yay!
Then I'll take up the migration of svn.collab.net to its new hardward
next week, *after* the release.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: The time for 1.3.1 is nigh
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Fri, Mar 10, 2006 at 01:53:16PM +0100, David Anderson wrote:
> When I volunteered for RM, it was with the understanding that I'd
> continue unless stated otherwise. So, yeah, if that's okay with people
> (ie. if I didn't do a too shabby job last time), I'm happy to RM for
> 1.3.1 as well.
Excellent!
> So, if you are satisfied with the state of the release branch, I can
> get an RC out the door this weekend. If not, I can help review stuff,
> or if you need more time to finalize things, just ping me when you're
> ready.
>
I'd like to hear what others think, but I think we should try to merge
at least:
* the fix to issue #2398, which fixes a potential server-side crash that
may or may not be exploitable in 1.3.0;
* r18721, which appears to be a regression in 1.3.0's Python bindings
that occassionally affects Trac; and
* r18665, r18668, which causes us not to show locks for 'svn ls' on
paths that needs URL-encoding.
It would be nice to merge the other changes as well, of course, but
if we don't get to them, I don't think we should delay the release.
We are expecting to release 1.3.2 when the BDB 4.4 support is available,
after all.
> Uh, actually, when you say "RC", what do you mean? My understanding
> was that for patch releases, there wasn't a soak + multiple RCs before
> release. Am I mistaken?
>
Nope - I just meant 'the RC that will become 1.3.1'.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by David Anderson <da...@calixo.net>.
* Malcolm Rowe <ma...@farside.org.uk> [2006-03-10 12:05:42]:
> So it seems like this has broad support, which is nice. I do realise
> that there was some ambiguity in my proposal of today as a target for
> merging the changes in STATUS (due to the combination of the imprecise
> phrase 'end of next week' and sending the mail on Sunday night).
>
> Anyway, regardless, we have merged some good fixes into 1.3.x since then,
> and theres only a few core fixes remaining unmerged, though it would be
> good to get them in (and the changes to contrib/tools as well).
>
> I realised that we're currently missing an RM for 1.3.1 (no, I'm not
> volunteering :-)). David, after your success with 1.3.0, were you
> planning on being the RM for 1.3.1 as well? [I'm not being entirely
> presumptous - you didn't run screaming when the idea was brought up on
> IRC :-)].
When I volunteered for RM, it was with the understanding that I'd
continue unless stated otherwise. So, yeah, if that's okay with people
(ie. if I didn't do a too shabby job last time), I'm happy to RM for
1.3.1 as well. And as I'm a little tied down in some non-svn stuff at
the moment, this'll give me a chance to contribute, even in non-code
form :-).
So, if you are satisfied with the state of the release branch, I can
get an RC out the door this weekend. If not, I can help review stuff,
or if you need more time to finalize things, just ping me when you're
ready.
Uh, actually, when you say "RC", what do you mean? My understanding
was that for patch releases, there wasn't a soak + multiple RCs before
release. Am I mistaken?
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Malcolm Rowe <ma...@farside.org.uk>.
So it seems like this has broad support, which is nice. I do realise
that there was some ambiguity in my proposal of today as a target for
merging the changes in STATUS (due to the combination of the imprecise
phrase 'end of next week' and sending the mail on Sunday night).
Anyway, regardless, we have merged some good fixes into 1.3.x since then,
and theres only a few core fixes remaining unmerged, though it would be
good to get them in (and the changes to contrib/tools as well).
I realised that we're currently missing an RM for 1.3.1 (no, I'm not
volunteering :-)). David, after your success with 1.3.0, were you
planning on being the RM for 1.3.1 as well? [I'm not being entirely
presumptous - you didn't run screaming when the idea was brought up on
IRC :-)].
Once we have an RM, we should set a date for an RC, I guess.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Ben Collins-Sussman <su...@red-bean.com>.
On 3/6/06, Arlie Davis <ad...@stonestreetone.com> wrote:
> Ah, I see. Sorry, still learning the process here.
Not much to learn here: only that 1.X releases are 'new features',
and 1.X.Y releases are 'bugfixes only'.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: The time for 1.3.1 is nigh
Posted by Arlie Davis <ad...@stonestreetone.com>.
Ah, I see. Sorry, still learning the process here.
-- arlie
-----Original Message-----
From: Malcolm Rowe [mailto:malcolm-svn-dev@farside.org.uk]
Sent: Monday, March 06, 2006 9:34 AM
To: Arlie Davis
Cc: dev@subversion.tigris.org
Subject: Re: The time for 1.3.1 is nigh
On Mon, Mar 06, 2006 at 09:07:23AM -0500, Arlie Davis wrote:
> I'd like to put in a request to get the windows service support patch
> checked in. It was reviewed and approved, but unfortunately the
> reviewer has been sick.
>
Sure, but that's for trunk (which will become 1.4), not the 1.3 branch.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Mon, Mar 06, 2006 at 09:07:23AM -0500, Arlie Davis wrote:
> I'd like to put in a request to get the windows service support patch
> checked in. It was reviewed and approved, but unfortunately the reviewer
> has been sick.
>
Sure, but that's for trunk (which will become 1.4), not the 1.3 branch.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: The time for 1.3.1 is nigh
Posted by Marc Sherman <ms...@projectile.ca>.
Arlie Davis wrote:
> I'd like to put in a request to get the windows service support patch
> checked in. It was reviewed and approved, but unfortunately the reviewer
> has been sick.
That doesn't have anything to do with 1.3.1, does it? When this patch
is committed, it will be on trunk, and I haven't seen any votes to
backport it to the 1.3.1 branch.
- Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: The time for 1.3.1 is nigh
Posted by Arlie Davis <ad...@stonestreetone.com>.
I'd like to put in a request to get the windows service support patch
checked in. It was reviewed and approved, but unfortunately the reviewer
has been sick.
-- arlie
-----Original Message-----
From: Malcolm Rowe [mailto:malcolm-svn-dev@farside.org.uk]
Sent: Sunday, March 05, 2006 3:46 PM
To: dev@subversion.tigris.org
Subject: The time for 1.3.1 is nigh
So we released 1.3.0 just over two months ago, and I think it's probably
about time for 1.3.1.
We've taken some fairly important fixes (see below), but the state of things
seems pretty much unchanged since djames' similar request at the end of
January - we're still waiting for the BDB 4.4 fixes. These aren't yet
complete on trunk, and - no offence to brane - I don't think we want to
release them directly into a stable release branch without the benefit of
exposure on trunk first.
So, could I propose the end of next week as a target for merging the
remaining changes in STATUS, for a release of 1.3.1 shortly thereafter?
And - in case it's not obvious - defer the BDB 4.4 fixes to 1.3.2.
Regards,
Malcolm
Changes in 1.3.x since 1.3.0 (mostly purloined from djames' message at
http://svn.haxx.se/dev/archive-2006-01/0924.shtml - including approved
changes in STATUS):
Core libraries:
- Fix crashes on mixed-case https:// URLs (r18042)
- Fix mv --force segfaults on unversioned files (r17242, r17243)
- Fix crash in svn status -u when an ignored directory is also in the
repository (r18291)
- Fix crash with diff and non-recursive checkout (r17231, r18539, r18541)
- Add missing error-handling checks, one of which was responsible for
server-side segfaults (r18249, r18196)
- Fix verbose list when used with peg revisions over ra_dav (r17485,
r18027)
- Make mod_dav_svn log all the errors in a given chain, rather than
just the first one
- Don't block waiting for background jobs of hook scripts (r18146)
- Set svn:date at the end of each commit, not the start (FSFS) (r18078)
- Strip peg revisions from the default name of checkout directories
(r18416)
- Support Neon 0.25.5 (r18215)
Client-side:
- Fix a regression which caused 'svn ci -m path_name' to no longer
require --force-log (r17956)
- Updates to svnmerge.py (various)
Ruby/SWIG bindings:
- Fix memory leaks (r17795, r17811)
- Fix character-set conversion bugs (r17726, r17925)
- Fix garbage collection segfaults (r17627)
- Fix the Ruby bindings compile error with SWIG 1.3.24 (r18456, r18458)
Python/SWIG bindings:
- Fix memory leaks (r18230)
- Fix assertion errors (r17792)
- Fix linking errors on Solaris 10 (r17910)
plus other miscellaneous changes (compilation: r18054, r18055, r18065;
packaging: r17829, r17831; default config file clarifications: r18247,
r18250).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org