Red Hat Bugzilla – Bug 809804
RFE: Persistent Revision History
Last modified: 2014-10-19 19:00:39 EDT
At the moment we don't have a revision history for the Content Spec that can be written into the package when it's created.
Should the Revision History information be stored in the Content Spec, or (more likely) as a Topic?
Then a parameter can be added to the CS Metadata Section:
And that Topic can be written into the publican assembly as Revision_History.xml
Ideally the revision history should be automatically populated. So basically you would need this first: Bug #731902. After that you could use the log messages as the revision history, though you'd need some mechanism to different random log messages to states that would be part of the revision history.
*** Bug 819720 has been marked as a duplicate of this bug. ***
Added in 0.32.0, syntax is as follows:
Revision History = [<ID>]
Revision History = [<ID>, rev: <REV>]
and it goes in the metadata section of a content specification. The topic itself must also be a "Revision History" topic as defined by the "Topic Type" tag.
I've also added validation rules to the builder to check that the <revnumber> fields are valid for publican and also that the revisions are in descending chronological order.
Moving this bug to CLOSED CURRENT_RELEASE to clean up old bugs that were QA'd by the PressGang team but not by the original reporter.