Managing development with two unlocked versions of one RuleSet
A developer asks:
We have two unlocked versions of one RuleSet undergoing development at the same time, and I'm concerned about mix-ups and gaps that could occur as a result.
For example, if Alice copies and changes a Version 01-02-03 activity into 01-02-04, but Harry also copies 01-02-03 into 01-02-05 and makes unrelated changes, Alice's changes might be lost when 01-02-05 is put into production.
Are there any recommendations or suggestions?
The type of concurrent development you describe, while sometimes necessary in a crunch, is discouraged for planned development.
The burden is on the team who make changes in the lower version to ensure that any necessary changes are also made to the higher version. Use the toolbar Siblings button to see in which versions a given rule exists.
Developers making changes to a rule in a lower version should be on the lookout for changes made to that rule in higher versions. If someone changes a rule in a lower version, and the rule also exists at a higher version, the change will be invisible to everyone on the higher version. They may need to apply her fix also to the later version.