On Mon, Jul 08, 2002, Bill Janssen wrote: > I'm not sure what this would help. Currently there's already a > release branch (stable), and the CVS tree (unstable).
Nope, currently there is an unstable tree (the main trunk) that still is kind of stable ;-) When we decide it is time for a new release it gets a new branch for the stable code. As soon as we make the release the stable branch is locked down and we are back to only having an unstable tree again. The unstable tree also has a few branches with new featues that are considered to be too unstable to be added to the unstable tree ;-) I would like to have a permanent stable tree that will continue to be developed (although not with any major changes -- mostly bug fixes) while we make the major changes to the unstable tree. This will make it possible for a user to continue using a stable version and get all bug fixes without being forced to start running an unstable version... /Mike
