We are about to move from SVN to RTC for source control. There will be several streams that after the move to RTC will need to be merged. Has this been a problem for anyone? Just not sure what to expect.
you always go thru a workspace to update a stream.. and u can deliver changes AND also Component add/deletes too..
should be simple..
we are helping a couple teams migrate from SVN as well. one has 20+ 'projects' that they deliver completely independently. so a stream for each (old trunk) and a new integration stream between the users (branch) and the book of record (trunk) stream.
The streams to be merged will have the same components and the history that is imported from SVN. Then of course any changes that are checked in between the migration from SVN and the merge.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPERMar 13 '14, 5:27 p.m.
One caveat on the "streams and workspaces" are cheap comment. It is true that streams and workspaces are cheap, and can be deleted at any time, but the change sets created by the import process cannot be deleted, so you don't want to try out the migration process in your production repository, because that will leave all those change sets taking up space in your repository.
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.
Comments
sam detweiler
Mar 13 '14, 2:50 p.m.same component in each stream or different?
Lisa Coker
Mar 13 '14, 2:55 p.m.The streams to be merged will have the same components and the history that is imported from SVN. Then of course any changes that are checked in between the migration from SVN and the merge.
sam detweiler
Mar 13 '14, 2:55 p.m.and streams and workspaces are cheap, they only contain pointers to the changesets, baselines and snapshots..
sam detweiler
Mar 13 '14, 2:57 p.m.so you would create a workspace from the contributing stream, accept/load
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Mar 13 '14, 5:27 p.m.One caveat on the "streams and workspaces" are cheap comment. It is true that streams and workspaces are cheap, and can be deleted at any time, but the change sets created by the import process cannot be deleted, so you don't want to try out the migration process in your production repository, because that will leave all those change sets taking up space in your repository.