AndrewW wrote:I would not be too reassured. When you use the Flare 7 Subversion integration, the UI gives the impression that you're using a Lock-Modify-Unlock workflow, when in fact it uses a Copy-Modify-Commit workflow. Even if you are trying to use Subversion with a Lock-Modify-Unlock workflow (using Subversion locking functionality), Flare 7 still uses a Copy-Modify-Commit workflow, but presents it as a Lock-Modify-Unlock workflow. From what I've seen, this can cause some difficulties. If a file does really need to be locked, or actually is locked by someone else, Flare 7 does not seem to take it into account, and gets in a horrible mess.
I agree with the above. During beta, I submitted a feature request for the UI to be changed so that, when you bind to SVN, your commands reflect what actual *Subversion* action you are performing. Otherwise, I really don't know what I'm doing when I have a file "checked out" or if I "Check In" a file. Can I even Get Lock, SVN-style?
I also asked for them to at least include a mapping (of Flare commands to SVN commands) and we don't have that, either.