Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I know this is sort of an old thread, but if others came by here I'dd share my personal experience.</p> <p>We have been using it over the past years here and as a headliner RTC has grown into a SCM I simply don't trust with my files.</p> <p>The workflows are so different that others SCM's so and as a whole the it's an over-complex and complicated system that from time to time causes you to lose your changes.</p> <p>The fact that there is an article over a supposed feature called the "Backup Shed" only tells the story that I am not wrong, the fact that there is the need of such a feature tells a story in it self about how changes can suddenly disappear. - <a href="https://jazz.net/library/article/191/?errno=1">https://jazz.net/library/article/191/?errno=1</a></p> <p>From other SCM's we are pretty much accustomed to that only "reverting" overwrites local changes. In RTC this happens on so many other occasions. One got to ask, how hard can it possibly be to merge files and/or conflict them in these situations?...</p> <p>RTC Will overwrite files when you:</p> <ul> <li>Resync your workspace, and since you can't check in from an out of sync WS, you can't avoid this, so by god, take a backup before doing so!</li> <li>Accepting Changes, yup that's right, despite what all other SCM's does... It will offer you to check in local changes before you accept changes however, so remember to click yes to that at <strong>PRAY</strong> that it had discovered all local changes.</li> <li>Random?... I am fairly sure have experienced other occations where changes vanished, but only the 2 above have been things I have been able to put a finger on...</li> <li>Revert... Obviously, the only one bullet that should actually be on this list.</li> </ul> <p>This may be by "design"... But then I would like to vote one for really bad design.</p> <p>Also as otherwise mentioned, if you are on Visual Studio, ALWAYS click refresh remote and local changes before checking in. A solution as subversion (as old as it is) are miles better at discover changes than RTC, and so is GIT...</p> <p>Besides, both SVN and Git have great implementations in many IDE's as well... I think it took a while until Git became tolerable to use within Visual Studio, but now it certainly is! Although there is still features to wish for. SVN can be integrated with many work-item/issue tracking systems as well but for the Jira integration, I actually just prefer to write the Issue numbers in the comments, it's faster and easier... And it creates the link as FishEye picks up the change sets, so Jira will display commits on issues.</p> <p>I can't say how Git/Stash combo or SVN vs. YouTrack/Mingle works here. But in RTC the workflow of attaching work-items to commits becomes this huge overhead so we stopped using it = Worthless feature.</p> <p>Then there is the whole planning, work-item, scrum etc. part of the system... The only part I will ever love about that is the laughs it gives me from time to time. Beyond that it's close to useless... Go Jira+GreenHopper, Mingle, YouTrack instead...</p> <p>One of the funny things is that IBM tries to sell this on "Integration" and how much you save on that... Since these solutions are so wide spread there are a ton of good solutions out there where you literally can set it up and won't have to touch a finger until you decide that it might be time to upgrade to a newer version of that software. Besides all that "supposed time savings on the administrators" just go in ten-folds for them to run around and help sort out many of the issues RTC seem to have brought.</p> <p>So I would advice against RTC. And Github, Codeplex, Bitbucket etc. has more than proven that things as Git, SVN etc. does in fact scale...</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload