Hi Dw,
We don't currently have version control integrated in the the environment, so the route you suggest is the way if you do want to do this. You can also use the publishing mechanism, and (re)publish your program at any point, and each version will then be available so it is easy to revert etc, but it is certainly not a full version control solution.
Our future plan is to look at using GIT to support this workflow, as the distributed nature could work very well for both publishing and individual development. But for the foreseeable future, the publishing mechanism or downloading to a local version control system is the best solution.
Thanks for the feedback; always good to hear desires in the form of questions.
Simon
What is the best way to go about repo integration and continuous testing ? Obviously any and all code worked on needs to be in some version control system the second it becomes something of some value; and right now the only way to do that seems to be to do a project export, unzip and commit to local svn. Is there a way we can reference a remote SVN repository (It seems that the import interface does not let me enter a non mbed SVN repo; even when I provide credentials in the URL).
Thanks,
Dw.