[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.0.2 release, when?

From: <kfogel_at_collab.net>
Date: 2004-04-01 21:17:25 CEST

"Sander Striker" <striker@apache.org> writes:
> I'd like us to consider 1.0.2 between one and a few weeks.
> We've seen quite a few bugfixes already, and with the proposed
> fixes in STATUS for backport I feel we have enough to
> warrant 1.0.2. It will also keep us excercised at doing
> releases ;).

I've no objection to 1.0.2 happening soon, if you (or someone) are
willing to drive the process. Unfortunately, in the next few weeks I
wouldn't be able to help much with reviewing and voting. I suspect
this may be true of the other Chicago developers too, though don't
want to put words in their mouths.

1.0.1's been pretty stable, and the diff to 1.0.2 wouldn't be that
huge, so I'm only +/-0.

(Btw, 1.0.2 would work with both Apache 2.0.48 and 2.0.49?)

Side issue:

In another thread, Justin said he didn't want to use any of the new
release procedures he and Ben are working on for 1.0.x release, rather
he would stick with the old release procedures for the 1.0.x line.

I think that's fine, as long as we have a 1.1.0-beta1, 1.1.0-beta2,
etc. In other words, there should be some chance to *test* the new
release procedures on real releases before 1.1.0 itself comes out.
That could happen with betaX releases leading up to 1.1.0, or it could
happen with 1.0.2.

I don't think it would be bad, per se, to use new release procedures
for 1.0.2. True, the goal of 1.0.x releases is to avoid instability,
but the current procedures have already caused instability in the
1.0.x releases :-), so the question is really one of relative risk.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 1 22:29:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.