From: George B. S. <gbj...@ho...> - 2001-10-18 04:15:37
|
I am glad Tom brought this up because I have been thinking along similar lines for some time. I think it would be a better representation of the DB package to advance the number closer to 1.0. Or to redefine the goals & requirements for what 1.0 means. I think people would think better of it and more readily accepts it's use if the number were 1.0. Further development can be defined to be a post 1.0 release. Comments? > From: Tom Dyas <td...@us...> > Date: Wed, 17 Oct 2001 23:40:12 -0400 > To: aji...@t-... > Cc: pil...@li... > Subject: Re: [pilot-db-list] DB 0.3.3 > > On Wednesday 17 October 2001 03:24 pm, Hans Ajiet Holtkamp wrote: > >> P.S. Can anyone explain the logic behind the >> version numbering 0.3.1 -> 0.3.2 etc.? >> I am unfamiliar with it, since I have >> mainly had experience with the Windows OS >> up till now. >> What do the first, second and third digits >> stand for? Does the "0" signify that this >> is not a finsihed product? > > When I was the maintainer, I numbered the very initial version of DB 0.10, > 0.11, 0.19. Then instead of going to 0.20, I decided to number it 0.2.0 to > match the GNU style for version numbers which is MAJOR.MINOR.PATCHLEVEL. Then > versions 0.2.0, 0.2.1, ..., 0.2.5 came out. When I changed the database > format to make it more extensible, I bumped the second version number to > 0.3.0. > > You are right, the initial 0 was for that fact that it was not a finished > product at the time. However, with all the great new features that Marc has > added as the maintainer and the contributions of others, DB may deserve a > 1.0.0 version number for its next release. It is up to Marc since he is the > maintainer. :) (Or maybe a "0.9.0" version number which usually means "It is > almost 1.0.0.") > > _______________________________________________ > Pilot-db-list mailing list > Pil...@li... > https://lists.sourceforge.net/lists/listinfo/pilot-db-list |