#288: Use proper numbering scheme
-----------------------+----------------------------------------------------
Reporter: kparal | Owner: jlaska
Type: task | Status: new
Priority: minor | Milestone: Packaging, Review, & Deployment
Component: packaging | Keywords:
-----------------------+----------------------------------------------------
Currently we release bug fixes by incrementing package release version.
That is probably incorrect, we should increment it only for packaging
changes:
http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Release_Tag
The release number (referred to in some older documentation as a
"vepoch") is how the maintainer marks build revisions, starting from 1.
When a minor change (spec file changed, patch added/removed) occurs, or a
package is rebuilt to use newer headers or libraries, the release number
should be incremented. If a major change (new version of the software
being packaged) occurs, the version number should be changed to reflect
the new software version, and the release number should be reset to 1.
Most project use this versioning scheme [1] (correct me if I'm wrong or
you have better terminology):
''major.minor.revision''
Major for large software changes, minor for smaller changes and new
features, revision for bug fixes.
The final Fedora package then looks like:
autoqa-major.minor.revision-release
This proposal is to change our versioning scheme to match the above one.
We will increment revision number for bug fixes (like hotfixing depcheck
and deploying to production) and revision increments for packaging
changes.
Ideas/concerns?
[1] http://en.wikipedia.org/wiki/Software_versioning
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/288>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
_______________________________________________
autoqa-devel mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/autoqa-devel
