Re: release proposal

Stefan.Fuhrmann_at_etas.com wrote:
> 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 ...

Here's the plan for Subversion:
Feb-21: alpha1
Mar-06: beta1
Mar-20: rc1
Apr-10: rc2
May-01: ga

(as you can see, they're already a little off :)

>> * 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?

That depends on whether Subversion releases another alpha.

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

I'd like to keep our alphas/betas/rcs in sync with the Subversion
project if possible.

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

Since a release takes a very long time, I'd like to make the releases on
the weekend. During the week I don't have that much time.
So if Subversion releases an alpha/beta/rc on a saturday, you guys won't
have that much time to react :)

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

I think the nightly builds should be enough. After all, we're in a lucky
position that much more people use our nightly builds than people build
their own Subversion binaries to test.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net