The current upgrade framework requires that all supported versions to upgrade from to have corresponding upgrade folders even though they might be empty. The folders are used to ensure the right scripts are applied to the right versions and to avoid upgrading unsupported versions. The problem is this is easy to forget during new release creation so upgrades might fail after release.
The current solution is to keep creating the missing upgrade folders. A better solution probably would include:
Proposed Milestone: 10.3 (per CS Meeting of 09/17/2014)
Also, the framework should support any lengths of version numbers (e.g. n.n.n, n.n.n.n).
After discussions with edewata and cfu involving moving PKI TRAC Ticket #1183 - Starting/stopping individual subsystems to Milestone 10.2.2, per request of edewata, we are also moving this ticket back from 10.3 to 10.2.2.
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.3
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.4
Metadata Update from @edewata: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 10.4)
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/1692
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.