Given the recent fuss over unstable release being uhm...unstable, here's a possible way to ensure
minimal release testing...
Instead of releasing, I create a branch in svn named something like 0.701-rc. The release manager
(yet to be appointed, not me) builds this branch, offers it to a group of dedicated testers (or on
the web in some obscure place where whiners do not go) and then
releases the version to the public (as unstable) adding a tag in the tags svn folder as is done now.
If there are problems with the release, the problems may either be solved in trunk and then merged
to the branch by the release manager, or fixed in the branch if they no longer apply to trunk
because of further developments.
This of course requires that someone becomes release manager (something that I'm not willing to do),
so if anyone feels inspired and wants to help out, this is the golden chance.
I'm also open to other suggestions that require little management effort on my part.
/J
|
