You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket covers the front end aspect of component and profile versioning/deprecation, originally Trac #142. Corresponding back end issue: #12.
Description of original Trac ticket:
Note: Trac #571 covers support for public drafts (publicly visible private components), a subset of the functionality described here, without the lifecycle status properties specified in CMDI 1.2
This enhancement should enable an owner of a component to designate a new component or profile as the new version of an existing a component, marking the existing version deprecated.
There will (at least initially) be no mechanism to deal with backwards compatibility, i.e. published components will remain unchanged but users will be strongly encouraged to use to the new version. The status will be represented in the XML/XSD of the profile (see #146).
This is the first and most important step after the required general component schema update in implementing the Component Lifecycle Management features of CMDI 1.2.
Also take note of the envisioned set of '''views''' that strongly relate to this (and the additional option to mark development components for review). See ComponentVersioning#Viewsworkspacesandregistries.
The text was updated successfully, but these errors were encountered:
This ticket covers the front end aspect of component and profile versioning/deprecation, originally Trac #142. Corresponding back end issue: #12.
Description of original Trac ticket:
The text was updated successfully, but these errors were encountered: