On Fri, 2001-11-09 at 15:11, Dom Lachowicz wrote: > I'm looking at this for a potential 0.9.5 release schedule: > Tuesday, Nov 13: 0.9.5-pre1 > Friday, Nov 16: 0.9.5 proper > We need to make sure that the menus are working properly everywhere and > that any final release-critical bugs (2130, imo) are fixed. > I also think that 0.9.5 should be the last proper relase in the 0.9.x > series and that our next releases should be 1.0 pre-releases or release > candidates. I was thinking of the following for a 1.0 release schedule: > Remember that 1.0 is neither the end nor the beginning, but an important > milestone in our product's development and general public perception.
I would suggest that we just make a 0.9.99 branch, which will lead to
1.0, and leave the normal tree for trying new stuff for the 1.1.x cycle,
which should lead us to a 1.2.0 version.
I would also suggest, in light of this, that we take a kernel like
versioning system.
That way: current cvs ---------------> 1.1.x ---> 1.2.0
\ merge all | bug fixes
+-------> 0.9.99 --> 1.0.0 ---> 1.0.x (only bug fixes)
How do you feel about this?
Hugs, rms
--
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Ghandi
+ So let's do it...?
msg19603/pgp00000.pgp
Description: PGP signature
