So, I've finished up a project in X1 and I'm ready to start a new project using the latest version of SONAR ... presumably X2.  Before I start I'd like to view a Groove3 tutorial video.  Here's the dilemma, I don't want to purchase an X2 video or start an X2 project if X3 is anywhere near being released.  I've heard way too many nightmare stories about starting a project in one version and trying to successfully port it to a newer version...no thanks!
 
I know there have been several threads trying to pin down a date for a pending patch or version release.  I'm not trying to get an exact date but it would be nice to get a ball-park estimate so that I can plan new projects.

I don't think Cake is going to give any hints as to when it will be released; they never have. I would just start the song in what ever version you normally work in. If it comes out while you are in the middle of working on it; save the song as a different name to start under a new version. That way you can always revert back to your last saved version.

I have constantly moved projects from an older version to a new update with no problems other than getting used to the new release's personality...

Of course there's an X3 coming but I doubt that will be released before October or so...

So, I'd think it fine to work in X2 in the meantime...

Keni

Even if X3 was going to be released next month (which would be too early if history is any indicator), you probably would not want to use it in a production capacity. We get some advanced notice of a new release when Cake starts the buy now and get the next release free promo (assuming they do that for X3 like they have in the past).

Sonar has a good track record of supporting moving forward with projects, so a project developed in 8.5.3 will open in either X1, X2, or X2a.  It does not work well to then try to go backwards, but in any case:
 
1.  If you have concerns about a particular project, simply copy the existing project folder and contents to a new project folder, and internally rename the project file to some variation on name from the old one.
 
2.  Once that is done, simply open the new one in whatever newer version of Sonar you wish, and have at it.  Your original project is safe and secure under its original name.
 
I have never heard of these 'monstrous stories' you referred to - perhaps you can elaborate.  There certainly are things one must do if moving older 32-bit plugins to newer 64-bit ones, but that is still quite workable.
 
Bob Bone
 

Use OMF files to transfer "Templates" to another version. Simply save the OMF and open it with the other version. I have mixed tunes from Sonar 3, 4 and 7 to X2.
 
Not familar with OMF files, read up on it.
 
Midi has to be in seperate OMF files. Audio can go as a set tempalte.
Many DAW's support OMF files.

Look, if you purchase X3 there is nothing stopping you from finishing a project in X1. X1 is a perfectly usable application. It will still work after X7 is released.  Once your project is reduced to stereo.wav nobody is going to know if it was created in X1 or X3. From a strategic point of view it might make sense to delay purchasing X2 or X3 for that matter until the version is about to be retired in the hope that the price will drop before the new version is released. The new version may introduce some ease of use features or a new bundled plug in or two, but it is unlikely it will add anything revolutionary to your current project. Finish your project with the version you own and buy the next version when the price or new features added make sense to do that.
 

Theycallmefree
Use OMF files to transfer "Templates" to another version. Simply save the OMF and open it with the other version. I have mixed tunes from Sonar 3, 4 and 7 to X2.
 
Not familar with OMF files, read up on it.
 
Midi has to be in seperate OMF files. Audio can go as a set tempalte.
Many DAW's support OMF files.

You are joking right? CW is very careful about making sure all new versions are backward compatible. With projects that are old just don't over write them. Always save with new versions with a new name. That way you can be sure that all your projects will stay compatible. 
 
The worst thing one could do is use OMF as a normal file for Sonar. You loose all editing and plugins that Sonar uses as well as routing and sends.  
 
The only reason to use OMF is if you have to transfer a project from Sonar to a totally different DAW like PT or Cubase. 
 

I've never, ever had a problem migrating an existing project to a newer version of SONAR. If it's really critical, e.g. for a paying customer on a deadline, just finish it up in the version you started with. All SONAR versions happily coexist on the same system and take up little space, so there's no need to ever uninstall older versions.
 
As for buying X2 now and then regretting it because X3 might come along, that's just something you gotta deal with in the software world. When I bought SONAR 5, we knew SONAR 6 was in the pipeline but didn't know when. Sure enough, S6 came out just 5 weeks later. I was pissed at the time, but the feeling passed. As for X3, I'll be surprised if it shows up before next January.

All good advice, however, the thing I'm most interested in is whether or not to lay out the cash for a Groove3 X2 tutorial at this time.  I just didn't want to spend the cash on the tutorial for X2 and then have X3 come out a few months later.  And just to be clear, I already have SONAR X2...'I just haven't used it on a new project yet.