Best way to maintain a library of subflows?
We have several libraries of subflows maintained by seperate groups within the company.
The current MOW is to take a copy of the library subtree into one's own tree to use the subflows. This allows the author to have access to a consistent version of the subflows.
However, it seems to cause a major mainenance overhead if you need to update the version of the library in use. As far as I can see, the only way to switch to a different version is to take a new copy and then update *every* reference to the library to use the new version.
Is there a better way of doing this?
Re: Best way to maintain a library of subflows?
I also do it like this ... every developer is responsible on his own way to assure actuality. I am the provider only and act as security and quality gate.