Steve Hosgood wrote:
But you could consider that after 1.0.0 things will change - if you make
it so. Have a rule that the only tarballs and other packages on the
FlightGear website are of the even subtree. Anyone wanting odd subtree
stuff must go to the CVS for it. Make sure that the even subtree doesn't
get covered in cobwebs (so to speak) such that no-one wants to run it
because it lacks all the cool new features (the 0.8 mistake).
Why the need for an odd subtree then?
Normal end users use the released packages on the webpage (currently
0.9.9). Everyone else, including developers and bleeding edge people
already check out from CVS.
One could branch the 1.0 tree in CVS and provide small fixes on that
while development of big stuff goes on on CVS trunk, but that's no need
for any change in version numbering. 1.0.x gets updated until trunk is
stable enough to release 1.1 or so. Like Curt said, a flight simulator
is not an essential system service where many other things build upon
and need a stable base. Normally pretty everyone should want future
updates as soon as they are stable enough for end users.
Don't start 1.1.x until at least 1.0.5 or 1.0.6 have come out so that
immediately post 1.0.0 the development team's efforts are aimed at
making dead sure 1.0.x will run properly. Linux kernel people rarely
start the odd subtree until at least ".10" of the even subtree is out.
Linux Kernel versioning has change a _lot_ since 2.6. There is not even
a real development branch anymore.
Nine
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
