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

Re: release proposal

From: <Stefan.Fuhrmann_at_etas.com>
Date: Sat, 1 Mar 2008 18:36:36 +0100

Stefan Küng <tortoisesvn_at_gmail.com> wrote on 29.02.2008 22:41:26:

> As some of you may have noticed, Subversion just released version
> 1.5.0-alpha2 (the first alpha was not released due to some problems).
> Which means that the final release is not very far away anymore.

Hopefully ;) My crystal ball says "somewhere" in June ...

> * release 1.5.0-alpha this weekend, linked against svn-1.5.0-alpha2
> we have to catch up with our screenshots (docs) a little bit: most of
> them are outdated and don't reflect the current UI.

+1. Do we plan for another alpha later or will this be the only one?

My suggestion would be that this is the only alpha for this month.
Many users (more than with subversion core project?) use TSVN nightly
anyway. So I don't see a need to release alphas frequently. If the
SVN beta should get delayed, we may still decide upon another alpha.

> * keep working on trunk
> * shortly after Subversion releases their beta, we also release a beta
> version for people to try and test, while we still keep working on
> our trunk.

+1. We should stay on trunk at least as long as SVN has not entered
the final release process starting with RC1.

In contrast to alphas, we should release beta versions more or less
in sync with the SVN project. That way people will have a consistent
tool set and the overall impression may be more "serious".

Since SVN releases are a bit unpredictable due to the signing process,
I propose that you post to this list once you are ready for beta and
people will be given 24h to react. Ship TSVN beta if nobody spoke up
against it.

> * when Subversion releases their first RC, we create the 1.5.x branch
> and of course also release an RC for TSVN

+1. These ~2 months of stabilization are much longer than for previous
TSVN release. However, the huge number of non-trivial changes warrant
such long stabiliazation periods.

Since SVN releases RCs quite infrequently, we may want to ship RCs
more frequently than SVN does, e.g. once per week. Alternatively,
we might provide nightlies for the stabilization branch.

> Basically, I'd like to postpone the creation of the 1.5.x branch until
> Subversion releases an RC. There are no big new features planned or in
> queue for TSVN until the final release anyway, which would mean that
> we'd have to merge back almost all our trunk commits anyway.

At least for my part, there are only smaller extensions to be made and
a number of leftovers to be fixed.

-- Stefan^2.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-03-01 18:42:13 CET

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

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