Guilhem Bonnefille <guilhem.bonnefi...@gmail.com> writes:
> For 1.0, I tried to import the idea of "stable" release (I then > released 1.0.1 and 1.0.2). I don't know if it was usefull or not, nor > if viking is sort of software that need such effort. The main idea was > to use even releases as stable ones and odd releases for > developpements (like Linux AFAIK). I guess the question is how much effort it is to be stable. > I also noticed that the numbering scheme based on using third digit > for bug fixes and second digit for enhancements is not easy: all > releases of viking contain both fixes and enhancements. I think that results from having it both ways. With 1.0/1.1 scheme, basically, hack on features release 1.1.2 hack more release 1.1.3 start to stabilize release 1.1.4 be comfortable release 1.2.0 hack release 1.3.0 bugfix on 1.2 branch release 1.2.1 The nice thing about bugfixes is that it plays well with packaging systems. If 1.0.0 is in a packaging system, and 1.0.1 comes out with just bugfixes (no new files, no ABI changes, no shlib bumps, no new dependencies - really just bugfixes), then it's trivial to update the package. If you don't need to release numbered tarballs for people to test during development before stable, then the whole even/odd is superfluous. An observation I often make is that once you tell anyone (who isn't primarily hacking viking) to use git or the devel version instead of the last release, it's a clue that a release is overdue. I'm a fan of the old gnu numbering scheme, which has 1.0.0 1.0.1 bugfix 1.0.80 1st alpha towards 1.1 1.0.81 2nd alpha towards 1.1 1.0.90 1st beta towards 1.1 1.0.91 2nd beta towards 1.1 1.1.0 release but it doesn't really matter. I would lean towards either gnu scheme or the even/odd scheme, but then only put bugfixes on the even point releases, and use odd point releases as needed, definitely having one before the even .0 release and then change only the version number.
pgpdcZLKGplDQ.pgp
Description: PGP signature
------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
_______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
