VAULT PRO QUESTION - NEW USER

[rcelebrado]

Good day.

Would like to ask how to solve the following scenario:
1. A working program was put in vault with a name of XXX labelled as rev000.
2. This XXX was checkout with on going changes by personA. The revision was not yet completed but check in.
3. Some other user personB check out again the XXX program and implement some changes without knowing that personA has an on-going revision on it. He then completed it and labelled as rev001.

Trouble:
1. personA revision was included on label 001 which should not happen, how to prevent it?


Thank you in advance.

[jclausius]

Can you elaborate some more on your example, is XXX a single file, a group of files, or perhaps a folder with a subgroup of files and folders?

If it is not too large a change, and you want to change the contents of Label rev001, someone could "edit" the label through promotion, and revert any changes from personA by changing to previous versions of files within the label.


Another option you may wish to investigate is branching. It might have been better to create a branch for each user, and have them commit to their branches, and then resolve the merge (using Merge Branches) in the folders at a later date.

For example,

$/XXX
$/XXX-ABranch (a newly created branch of $/XXX)
$/XXX-BBranch (a newly created branch of $/XXX)

personA commits to $/XXX-ABranch, personB commits to $/XXX-BBranch, and when each is deemed ready, they can individually merge changes using Merge Branches from XXX-ABranch and XXX-BBranch into $/XXX/