Best practices for implementing "vendor branch strategy"
![]()
What are the recommendations for "best practices" for implementing a "vendor branch strategy" with RTC source control?
We are currently using 4.0.3 and will be upgrading in the next few days to 4.0.6 RTC server and client. One member of our team (with the most experience with RTC among us) believes that we should do it with workspaces and base-lines without creating an explicit stream for the "vendor branch", but I am concerned about the long-term maintenance of that compared to creating a proper stream. I see the potential for problems when we want to look at the history of changes and I am worried that while it may be easier in the short-term, it will introduce complexity in long term maintenance e.g. depending on naming conventions on base-line labels.. Also, if we implement a "vendor stream" is it better to have a single stream that is for all vendor drops, or separate streams for each vendor / component? I am looking for advice on "best practices" from people with more experience than we have here with RTC which is very lacking here (we recently migrated from perforce and this group has not used a vendor branch in the past. Thanks. |
One answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.