From: Ethan M. <merritt@u.washington.edu> - 2004-02-18 18:19:34
|
On Wednesday 18 February 2004 10:00 am, Lars Hecking wrote: > > In other words: I would propose an immediate code freeze of all the C > > sources (only bug-fixes, and then only if they're small), a release of > > 3.8k ASAP, and a release of 4.0 on, say, Easter (mid-April). > > No objections. Altough I think code freezes have never worked around > here ... Is it possible to proceed in the following stages? 1) release 3.8k 2) branch off a clean tree for a code-frozen 4.0 3) rename the main CVS development tree 4.1a 4) allow development work to continue in the 4.1a tree 5) bug-fixs (only) get applied also to the frozen 4.0 copy 6) release the 4.0 version in April -- Ethan A Merritt merritt@u.washington.edu Biomolecular Structure Center (206)543-1421 Mailstop 357742 University of Washington, Seattle, WA 98195 |