Hi, I’m afraid there isn’t a way to switch between them. And m3 isn’t (currently) looking like it will be fully compatible with m2… so I’d definitely recommend v0.1.2 with regard to stability (there are no further plans to change it).
The trouble is that the milestones need to change to support new features that couldn’t possibly fit into v0.1.2, and I’m finding more and more changes necessary as I go along. I’d like to be able to say they will/can be backwards compatible, but achieving that would make the task enormously more complicated and slow things down even further - and for now it’s still just me working on it in whatever time I can scrape together. I’d rather make the more painful changes sooner rather than later, and grow the number of developers beyond 1 to make everything more sustainable.
Nevertheless, I’ve tried to keep the actual .qpdata files for v0.2.0-m2 compatible with the .qpdata files of v0.1.2. Therefore potentially you could create a project containing the same images in v0.1.2 and track down the corresponding .qpdata files, copy them in the ‘data’ folder and rename them in a v0.1.2-friendly way.
In any case, my intention is to try to get things stabilized as quickly as possible, and then figure out some way (likely via scripts) to move things over to the more stable version.
For now I can’t help very much with transitioning between versions, since every precious coding moment needs to go into making things stable sooner…