Allow Xlinks to target branches in addition to changesets
Xlinks in this way would point to the most recently committed changeset on the target branch branch, rather than just a specific targeted changeset. If need be this might have to be a read only Xlink.
This added functionality, especially in conjunction with partial Xlinks, would allow for very dynamic repository creation.
Matthew Wilde
shared this idea
We can’t break cset immutability.
-
Maurizio Margiotta
commented
If we can't get and xlink targeting a branch, could we have a view where we can see all the xlinks that could be possibly updated to a more recent changeset, and from here to chose what to update?
Now the workflow is terribly slow, as for each xlink I have to search for the folder, edit xlink, select the last changeset. With partial xlinks spread in different places, this becomes really annoying. -
Adminpsantosl
(Admin, plasticscm)
commented
Hi Mattew,
No way we can implement this.
Look, the beauty of changesets is that they're not only a way to group files when you perform a checkin, they're also a "rollback point".
A "changeset" represents a "working tree" as it existed on your workspace and you can jump back to it at any moment in the future and reproduce the exact configuration you had.
If we allow xlinks to point to a branch, then we can't guarantee you are going to get the same when you go back to a given cset: the configuration will be dynamic, hence breaking the basic principle of changesets.
In fact, we used to allow "dynamic" rules prior to 4.0, but we learned they were more error prone and hard to understand for most users, so we got rid of them. Now we stick to immutable changesets.
Please do not hesitate to ask.