SVN Version control issues

[Guillaume]

I'm aware that many people have dropped and discourage using SVN + EA due to a number of issues.
As I have a number of customers that need the "Undo Check Out" feature to roll back, and since EA security feature doesn't fulfil this need, I currently have to keep this configuration. (if someone has identified an alternative to VC that provides a rollback/undo feature, I'm interested!)

I was wondering if there is any recommendation to avoid the following issues when using a central DB (SQL Server) coupled with SVN:
A number of users have experienced a desynchorisation between SVN and EA i.e. we can end up with an empty controlled package that cannot be checked out since the SVN lock remains on the repository, yet not seen by EA. Hence I have to run an EA/VC resync, followed by an undo check out so it all comes back to normal.

Worse case: a user had a number of uncommitted changes in the central DB and a desync between EA and SVN occurred ; the package was locked in EA so he could no longer update his package. Running a resync from a different user reloaded all data from the XMI and deleted the uncommitted changes !  :-/ I take that this would have been prevented if it had been run from the same user.

What is Sparx view on these ongoing issues between EA and VC repositories? Is there anything planned in this area?

Guillaume