M4rtin
If you have multiple working copies in a project that are version 1.7 the conversion fails with a message that no working copies have been found. With a single working copy in a project it works. This should really be fixed, otherwise conversion will be a true pain.
liam.mclennan
Hello M4rtin, I tried to reproduce this problem but it worked fine in my test environment on Win7. I had multiple working copies in one project that I worked on in SmartSVN 7.6.x (Subversion 1.7). Upon upgrading to SmartSVN 8rc3 I was able to check this project out and successfully upgrade to Subversion 1.8. Is the perhaps any other detail you could provide us with that might help us reproduce this problem? Out of interest too, how many working copies are we talking about here in your project? P.S. If any other readers have experienced M4rtin's issue please let us know and give us some details about what you are doing before seeing the error.
ericjs
Will this new versions require you to upgrade your working copies to 1.8 format to use them? I also use kdesvn which does not support 1.8 yet, and would like to keep my local copies compatible for now. (Kdesvn is not very good...which is why I bought SmartSVN for any major svn tasks, however Kdesvn has file explorer integration which is handy to use on occasion.