On Tue, 16 Feb 2016, Donald Sharp wrote:
In today's Monthly meeting we briefly discussed how we would like to
version Quagga going forward. Two proposals were put forward, a date based
version string or a Major.Minor.Bug version string. I'd like to propose
that we combine the two of them together and get this:
Major.Minor.YYYYMMDD
Major = Major restructuring/Feature added to the system, VRF comes to mind.
Minor = Minor restructuring/Feature added to the system. The MTR code
changes or the zebra refactoring that has been going on comes to mind.
YYYYMMDD =
YYYY - The Year of the release
MM - The Month of the release
DD - The Day of the month of the release
In the unlikely event we need to release a bug fix on the same date add
something like a -1 to the end, or wait till tommorrow.
;)
A little comment. We often tend not to do "major" v "minor" releases.
Just releases, as and when they are needed. Also, some daemons might
have major changes in a release, and others minor. Some fixes may be
minor to one user, major to another. It's really hard to make a globally
consistent determination of wht is "major" and what is "minor".
Possibly "new features or compatibility breaks" v "bug fixes to existing
features" is a distinction we could sort of make.
On date, I've long used the CONFDATE to put the date configured was run
into the version string of RPMs built from within Quagga, along with a
2-digit revision suffix (to deal with the 'same date' issue).
That said, I'm not sure I want the date in the version. :) I'd prefer
just bumping a number.
Not very helpful, I know, sorry.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
Harp not on that string.
-- William Shakespeare, "Henry VI"
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
