Some years ago Microsoft put out a very well thought out "best practices" document on version numbering. It covered these issues as well as others.
As a minimum the document would be well worth studying. I would provide a link, but I am doing this from a hotel room. :-) Karen On Sat, Aug 7, 2010 at 2:24 PM, Robert Martin <[email protected]> wrote: > On Sat, Aug 7, 2010 at 5:15 PM, Justin Clark-Casey > <[email protected]> wrote: > > We could do this but then we approach 1.0 very rapidly (0.8, 0.9, ...) > which > > would imply some kind of 'completion' and I think that we're still some > way > > off that point. > > > > We could go into 0.10, 0.11, 0.12, ... but this seems to be confusing for > > people. > > what i might suggest is going to a style of say N.X.Y with Y being a 4 > digit number > so we could do a bug fix version as 0.7.0010 which would be replaced > by say 0.7.0020 which would be replaced by say 0.7.0040 ect > > personally i am all for having a bin release any time a nontrivial bug > gets fixed. > > -- > Robert L Martin > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev >
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
