Hi, Is it possible to branch an Oak repository and maintain a detached root node for a period of time that one or more Oak instances attached to a MongoDB instance can follow for a short period of time before merging the "branch" back into the main tree ?
Although there may be conflicting changes, I would like the main tree to take precedence on merge. I am thinking of a cluster containing a number of instances where changes are made to a subset of the cluster prior to allow those changes to tested before the whole cluster is exposed to those changes. ie managed repository content upgrade. Best Regards Ian
