svn 1.1: All aboard. Train is leaving the station.

It's been almost exactly a month since I did an issue sweep and sent
email about freezing for the 1.1 release. Things are looking good;
all the 1.1 issues have been fixed and closed, as well as a whole
bunch of "1.1-consider" issues.

I want to push to finish whatever we can this week, then do our 1.1
code freeze on the weekend. The train is finally leaving the station;
if a bug or feature isn't ready by the end of Friday, then it will
have to catch the 1.2 train. :-)

In a separate email, I'll attempt to summarize where we stand on the
remaining 1.1-consider issues. In this mail, I want to ask a
meta-question about the release process.

We have two possible courses of action:

  1. Freeze /trunk. Roll beta-tarballs from /trunk. After 4 weeks
      of freeze, we release 1.1 and copy /trunk to /branches/1.1.x.

  2. Copy /trunk to /branches/1.1.x. Roll beta-tarballs from the 1.1
      branch. Allow new development to continue on /trunk. Do a
      release after 4 weeks.

Subversion 1.0 was a Really Big Deal. Our reputation was at stake, so
we followed procedure #1 above. The rationale was that this forced
developers (and not just tarball testers) to use the frozen code for
daily work.

But 1.1 is not quite as big a deal. Subversion is pretty well
established already; our main audience is users upgrading from 1.0.
It's likely that we'll get quite a number of users QA'ing the beta
tarballs, and it's not so clear that it's worth halting all new /trunk
work for a month as a way of "forcing" developers to test.

In any case, you can see which way I'm slanted. But I'd like to hear
opinions from other folks about how to proceed.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 21:51:27 2004