The topic of version and baseline was raised at the most recent user forum - and also discussed during user engagement during December 2018. The notes from both sessions are below
-Version control is the tracking of changes to content over time
-Baseline is the declaring and managing of “known” good points over time
-A repository may never have baselines applied.
-A repository may start with no version control or baseline applied to it
-At the point a repository is declared as being in a baseline, change control processes are typically put in place to accept changes to the content.
-It is desirable that baselines are drawn around collections of items, at the definition of the user. (eg: around modules of a solution)
-It is desirable that all items in a repository are versioned. Each change implementing a next in sequence for the version.
-For Elements, changes to name, fields, relationships and items on the element’s model canvas all increment the version.
-Items in the library area should also be versioned.
-A user is likely to wish to understand differences in baselines.
-It is desirable that the user is able to roll back to earlier baselines.
-It is not anticipated that a user will need to roll forwards / backwards versions of elements outside of the baseline process.
It is desirable to see the version history of items, but maybe only changes
Please sign in to leave a comment.