Yaboto version numbering.
acrux_it at libero.it
Fri Oct 21 07:39:23 EST 2011
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 20 Oct 2011 11:55:43 +1100
Tony Breeds <tony at bakeyournoodle.com> wrote:
> Hi all,
> I'm thinking of changing the yaboot version numbers. The
> current "1.3" portion is pretty meaningless, all I do is update the
> 3rd number with a new release.
> So I'm thinking of changing the numbering scheme to be something like
> 1.$major.$minor With the typical meanings for major and minor.
> So the next release would be 1.18.0, then I can add trivial bugfixes
> and bump the minor number. Which will hopefully make it easy for
> distributions to track a released branch.
> Once 1.19.0 is released the 1.18.x branch wouldn't get anymore
> Any objections?
imho, i'd avoid to to have a new release with 1.1x.y because is minor
then the old release 1.3.x . It'll offend any distro's maintainence
tools that normally just simply parse the release number to notify an
I can just suggest to use 1.3.x for any minor bugfix and bump
to 1.4.x or 2.x.x for the next future major release.
With a reworked ofpath (finally able to understand modern kernels device
names) the 2.$major. $minor could really be the best choice.
> I'm particularly keen to hear from distribution package maintainer on
> how that scheme will work with their distribution.
i'll wait for other suggestions too.
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Yaboot-users