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.
First, create a Beta line off the 0.35.0 tag:
$ svn cp -m "Create branch for Beta / 1.0 stabilization." \
http://svn.collab.net/repos/svn/tags/0.35.0
http://svn.collab.net/repos/svn/branches/1.0-stabilization
Note that the word "Beta" does not appear in the branch name, just as
the word "Alpha" doesn't appear in our current interim release names.
Beta is a state of mind that may apply to various interim releases,
and its goal is to reach 1.0. We don't want to spend a long time in
Beta, just long enough to shake out important bugs.
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, but many trunk
changes will *not* be ported over to the branch. 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. We've always known
there would be open issues when we ship, that's just the way it is on
an active project. We need to avoid the temptation to close all of
those issues for 1.0 :-).
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.
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.
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.
It's not my intention here to start a thread about where the 1.1.X
line is going (i.e., about the definition of 1.2). That's a separate
conversation, which we can have later. This is just about 1.0.
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.
Questions? Comments? Fresh vegetables?
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 4 05:56:29 2003