#1210 New versioning scheme
Closed: fixed Opened by edewata.

The Dogtag version number consists of 4 numbers (..-). Currently the use of these numbers is not very well-defined and may not conform to some packaging guidelines.

The numbers should be used as follows:

  • The number should indicate a major architectural change, a major rewrite, or a set of new major features. Backward compatibility may not be guaranteed.
  • The number should indicate incremental changes over the last major change. New features can be added, but backward compatibility should be maintained. Old interface should be preserved but it can be deprecated.
  • The number should indicate bug fixes over the last minor change or insignificant changes that only affect a limited scope.
  • The number should indicate RPM packaging changes. The source code itself should not change, but patches can be applied on top of it by the RPM spec file.

Proposed milestone: 10.3


Per CS/DS Meeting of 11/24/2014 - 10.3

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

This versioning scheme has been in use since 10.3.0.

Metadata Update from @edewata:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.3.0 (was: UNTRIAGED)
- Issue status updated to: Closed (was: Open)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1772

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata