I've created a REL1_4 branch in CVS. To update your existing HEAD working directory:
cvs up -dP -r REL1_4
To pull a fresh copy (as a developer):
cvs -d:ext:username@cvs.sourceforge.net:/cvsroot/wikipedia \ co -r REL1_4 phase3
(If you're using Sourceforge's anonymous CVS server it may take a few hours before the update goes through there.)
The release branch frees up CVS for more experimental code, while REL1_4 should now concentrate on getting what's already in there stable and working. We'll tag and release a few beta versions over the next couple of weeks, with a 1.4.0 final release when the main things are ironed out.
If we make additional 'big' changes before release, they should be done in HEAD first. Bug fixes should naturally go both in REL1_4 *and* the head branch.
As far as future scheduling: I would very much like us to start getting releases out on a faster schedule, each with tighter changes more concentrated on particular areas than the swamps we've done in the past. Aiming for 1.5 in February would be nice (~2 months from 1.4). We'll do some planning on future directions at the 21C3 conference in Berlin in late December.
-- brion vibber (brion @ pobox.com)
On Wed, 2004-01-12 at 01:08 -0800, Brion Vibber wrote:
If we make additional 'big' changes before release, they should be done in HEAD first. Bug fixes should naturally go both in REL1_4 *and* the head branch.
Doesn't that make merging between branches hard for you?
In any event: I have about half-a-dozen more hook events to add to the codebase -- mostly stuff about viewing articles, or in the skin. I'm going to add them to the REL1_4 branch, since I figure a half-built Hooks feature is not good for anyone.
I'm also going to add a compatibility hook for $wgCallbackFilter at the end of Setup.php, after all the extensions are run.
~ESP
wikitech-l@lists.wikimedia.org