> Our last planned interim milestone in Alpha is 0.35, which is
> scheduled to be code-complete on Friday, 12 Dec. (There are two
> issues remaining, one of which -- #1601 -- is still under discussion,
> but we should be able to get it wrapped up by the 12th.) The 0.35
> branch will sit for the usual one week soak, then we'll tag it and the
> tarball will come out on 19th December.
>
> At that point, I think we're ready to enter Beta. Here's a plan,
> comments welcome of course.
I better get those changes for my issue 897 checked in fast! :-)
[ snip the part which explains the process; I agree ]
> Hence the name of the branch, "1.0-stabilization". The point of this
> branch is to terminate in a 1.0 release. Trunk development will
> continue in parallel with the 1.0-stabilization branch,
Good.
> but many trunk
> changes will *not* be ported over to the branch.
Very well.
> Exactly which
> changes get merged and which don't will be decided by the release
> manager (Jostein), in consultation with the developers, but the
> general goal is to avoid destabilizing the branch.
This (potentially) puts a lot more work on the hands of the release manager.
Maybe we should consult Jostein if he has this amount of time available
after we agree that this is how it is going to work.
[ snip the open issues part ]
And now onto the most user-visible part of it all ...
> During the Beta period, we will put out interim releases (0.36, 0.37,
> and so on) from the 1.0-stabilization branch as necessary. I think we
> should not bother with releases from the trunk during that time.
I agree that *during stabilization* we should not release from the trunk.
From a reaction I understood that people understood this to be that we won't
release 1.1.1 before 1.0.1; I don't think you made any statement for the
situation after 1.0 (yet).
and onto 1.0....
> After 1.0 comes out, we can start putting out development releases
>from trunk again, named "subversion-1.1.X.tar.gz", with X increasing
> each time. Simultaneously, we should maintain the stable 1.0 line for
> critical bugfixes, with (less frequent) releases, named
> "subversion-1.0.X.tar.gz", with X increasing. No new features would
> ever be introduced in the 1.0.X line, of course.
And here you did not say that there will be no releases for 1.0 while
releasing from the trunk. Did you?
> This is essentially the "even==stable, odd==dev" scheme that many
> other projects use. I've already renamed the "1.1" milestone to "1.2"
> in anticipation of this, so that we can release 1.1.X tarballs and
> have it be understood that a) they're leading to 1.2.0, and b) any fix
> present in a 1.0.X release is also present in all 1.1.X releases,
> either by implication, obviation, or direct merging. We'll document
> all this clearly on the web site, of course.
I think this is very clear. One question though: From the 1.0.X and 1.1.X
part I conclude that we will be releasing fixes for 1.0 and fixes and features
for 1.1 in equal pace? i.e the X in 1.0.X was intentionally the same X as the
one in 1.1.X?
> Naturally we can't be certain how long the 1.0-stabilization branch
> will last, but I'm hoping not more than a month or two -- in other
> words, a 1.0 release sometime in the first few months of 2004. The
> exact date will depend on what we discover in testing.
Looks like a fine goal to me.
> Questions? Comments? Fresh vegetables?
Since it's my birthday; I'll have cake please :-)
bye,
Erik.
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 4 18:43:48 2003