Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've been using Surround SCM at my job and I'll say it is what it is, but there are a few things that I find lacking. Though, I've heard that surround scm integrates well with surround's issue tracking system, but I can't comment on that because we don't use that.</p> <p><strong>I personally find the UI to be buggy and confusing.</strong></p> <ul> <li>The workflows are confusing and often offer you with prompts that don't apply, so you get used to ignoring warnings. <ul> <li>eg. "are you sure you don't want to auto-merge?" "Are you sure you want to overwrite files?" </li> </ul></li> <li>The UI always badgers you to use the auto-merge feature but every time I've tried it, it ends up messing up my code (C#).</li> <li>On top of that, the packaged diff tool (Guiffy) is buggy and doesn't display text properly.</li> <li>Weird workflow quirks can result in your changes being overwritten.</li> </ul> <p><strong>It doesn't do directory syncing</strong> ...which means that every time you add a new file to your project you must by-hand go and add it to the SCM repository. If you don't, everything will look normal to you until one of your teammates emails you because you broke the build.</p> <p><strong>There's no good way to copy over revision histories when you are branching</strong> ... which means that you are less likely to branch when you should be. There's nothing more frustrating than to have to store code locally because you're making changes right before a release and your team refuses to branch the code into another repository.</p> <p><strong>There's no good way to blacklist certain files from being checked-in or from being overwritten during an update.</strong> If there's a file that you don't want to check-in then you're left with the painful chore of scanning through a long list of files and deselecting those you don't want every time you want to check-in. Yuck.</p> <p><strong>Features aren't documented that well</strong> Of course, they release a user's guide but it's about as helpful as Microsoft Windows help function. It tells you step by step how to do things in the UI (ie. "click 'Create Shadow Directory', then click 'OK'", but it doesn't tell you what those features are, how they are intended to be used, what actually happens server-side etc.</p> <p>Btw, if you know of any good way to get around these problems let me know :)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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