GNOME Bugzilla – Bug 757736
Programming guidelines: problems in the versioning page
Last modified: 2015-11-13 09:29:07 UTC
The application versioning guideline is wrong: https://developer.gnome.org/programming-guidelines/unstable/versioning.html.en#application-versioning AFAIK all GNOME applications have a micro version for bug fixes and translation updates, not "major.minor". Another thing worth explaining is the odd/even minor version convention, and the 6-months release schedule.
(before writing patches I prefer to have your opinion)
(In reply to Sébastien Wilmet from comment #0) > The application versioning guideline is wrong: > https://developer.gnome.org/programming-guidelines/unstable/versioning.html. > en#application-versioning > > AFAIK all GNOME applications have a micro version for bug fixes and > translation updates, not "major.minor". Yes, include that. These guidelines were (apparently, badly, sorry) adapted from another project which doesn't use micro versions. > Another thing worth explaining is the odd/even minor version convention, and > the 6-months release schedule. I would mention the odd/even version convention as one convention which is followed by most (but not all) GNOME modules. I don't think the release schedule is relevant here in an explanation about versioning systems.
Created attachment 315083 [details] [review] programming-guidelines: micro package version for apps too Restructure the sections. Since the package versioning is the same for libraries and apps, have the "Package Versioning" section in common. And have a "Libtool Versioning" section.
Created attachment 315084 [details] [review] programming-guidelines: odd/even versions for stable/unstable releases
Review of attachment 315083 [details] [review]: ::: programming-guidelines/C/versioning.page @@ +64,3 @@ + The package version number is that passed to + <code>AC_INIT()</code>, and the one which is typically known as the + project’s version number. For example, the Debian package for a library s/'/’/ (and in other places).
Review of attachment 315084 [details] [review]: ::: programming-guidelines/C/versioning.page @@ +160,3 @@ + new features, only translation updates and bug fixes. On the other hand, + a new micro <em>unstable</em> version (e.g. 3.19.1 → 3.19.2) can add new + features. Unstable micro releases can also add API, or change or remove API which was added in a previous micro release in that minor series.
Thanks for the review. The first patch doesn't need to be updated since it doesn't contain single quotes ', only ’.
Created attachment 315238 [details] [review] programming-guidelines: odd/even versions for stable/unstable releases
Created attachment 315239 [details] [review] programming-guidelines: typography fixes
Created attachment 315240 [details] [review] programming-guidelines: add some missing markup in documentation.page While I'm at it.
(In reply to Sébastien Wilmet from comment #7) > Thanks for the review. The first patch doesn't need to be updated since it > doesn't contain single quotes ', only ’. Huh, looks like Splinter helpfully reformatted them as straight quotes, or used a font which does. My apologies.
Review of attachment 315238 [details] [review]: ++
Review of attachment 315239 [details] [review]: ++
Review of attachment 315240 [details] [review]: Super!
Attachment 315083 [details] pushed as 3670de8 - programming-guidelines: micro package version for apps too Attachment 315238 [details] pushed as fefa778 - programming-guidelines: odd/even versions for stable/unstable releases Attachment 315239 [details] pushed as 247bad8 - programming-guidelines: typography fixes Attachment 315240 [details] pushed as 4d271c2 - programming-guidelines: add some missing markup in documentation.page