I'm a new user, and couldn't find this particular issue in the documentation, and know it will be something I'll encounter often:
What is the recommended workflow to handle document changes in Scroll Versions for intermediate releases that are created -after- a "later" release?
For example: My current content is all in v1.0. I create a version 2.0 (with 1.0 as the preceding version) and start creating page updates to reflect 2.0's changes. The version tree is nice and linear, awesome. Suddenly, we need a 1.5 release, so a 1.5 version is created, also using 1.0 as the preceding version. I have to add in v1.5 changes to the same page that will also house v2.0 changes. The version tree is now branched.
I would expect that i'd be able to make the v1.5 changes, then either: 1) Merge 1.0 and 1.5 together, and those changes should be carried through to 2.0, or 2) Change the "Preceding Version" for 2.0 to v1.5, making the tree linear again. However, when I tested these out, neither of these options appear to actually include the 1.5 changes in the 2.0 versions of the pages. Can you clarify the recommended process to handle this type of situation?
Please sign in to leave a comment.