Planned maintenance window - archimatetool/archi-modelrepository-plugin GitHub Wiki

[!WARNING] There are two really important rules to follow while using the collaboration feature of Archi:

• You should never move a folder or change folder content if you're not absolutely sure that nobody will edit some of these objects at the same time. Doing so would lead to conflicts in which some objects appear to be deleted or new, and whatever option is chosen (mine or theirs), you'll end up with a message saying that "File is not directory or folder.xml does not exist" and the model will be corrupted.
• You should never merge elements or relationship if you're not absolutely sure that nobody will edit some of these objects at the same time. Doing so would lead to conflicts caused by views that have been automatically updated to account for the merge.

To avoid these issues, it is highly recommended to plan some maintenance window:

1. Some days in advance, send a communication to your colleagues:
   • Explain what you intend to do.
   • When these changes will take place.
   • Ask them to publish their changes before and to wait for your feedback before editing the model.
2. Before the chosen day and time, everyone should have publish their changes. It is nonetheless usually a good practice to send a gentle reminder.
3. At the chosen day and time:
   • Publish your own, previous, changes. This will make sure the remote version on the server is up to date with any potential conflicts solved.
   • Do the needed impacting changes (folder reorganization or merge of concepts).
   • Publish these new changes. Make sure you use an explicit commit description.
   • Send a communication to your colleagues. Be sure to tell them they must run a refresh before working on the model.