[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: Ben Reser <ben_at_reser.org>
Date: 2004-04-02 10:59:06 CEST

On Thu, Apr 01, 2004 at 01:17:25PM -0600, kfogel@collab.net wrote:
> 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'm with Justin. I haven't really had time to dig into this yet much
myself. I'm just getting caught back up with the email here right now.
I'd rather do 1.0.2 the way we've been doing it. The exception to that
would be pax. Which I swear I'm going to get a test tarball put up
soon. Maybe tomorrow if I can find the time.

> 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.

Make sense to me.

> 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.

I think it's more of a we haven't had time to really get anywhere on
this than a risk issue.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 2 10:59:27 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.