Cisco Systems (maker of the market majority of Network Infrastructure equipment) uses a method that is necessary from a liability standpoint or loss of revenue, but it works quite well. If you read the Release Information on a specific code release, you can see Resolved and Open Caveats for each release. The idea, obviously, is to see if your symptom was resolved in the latest version, or if a bug that could impact you has been reported in the latest version.
 
Although I would love to see this, along with small hot-fixes/patches from Cakewalk for Sonar, I don't see this happening because the liability and demand aren't quite high enough. I'm they have this internal, but not where we can see it. Plus, Cakewalk doesn't provide sub-releases beyond a,b,c,d, which I believe is analogous to Microsoft Cumulative Service Packs, vs. a series of patches and fixes.
 
It's an older school way of doing things, IMO, but if it works for them, then so be it. X3 has so far been good, although I half expected more new things, but if they spent much of the time fixing issues/bugs and working more closely with the code to make it more solid, we're going to get a long just fine.

X3 looks amazing. I want it.
 
However, my experience of X2 was frustrating to say the least. I will upgrade only when I am confident X3 is more stable. For now I will observe the forums. A bug fix list would definitely make the process easier...
 
Specifically, I would like to hear if the following bugs have been fixed:
 
1: Changing between screensets caused Sonar to freeze momentarily and sometimes crash.
2: Clip fade ins/outs had no effect on some audio clips.
3: R-Mix caused some insane stuff to happen - like disappearing MIDI information, even once you disable the plug in and took it out of the project.
4: Sonar 'infected' some projects rendering them full of irreversible bugs.
 
I'm enjoying reading all the positivity on the forums at the moment - I really really hope X3 is a solid, stable success. Very curious.
 
Dave

If you're using X2a today, here's what I recommend to do to help your upgrade go smoothly:
1) Download the 4-part install and go through those instead of ordering media (as I hear the download is a later build). Register the serial # as normal during the install.
2) Open Sonar X3, let it run driver/interface tests, and go to Edit/Preferences. Go to VST Settings and uncheck replace VST2 plug-ins with similar VST3 (not perfectly sure on the wording).
3) Scan your plugins through the Plug-In Manager, but make sure you've added any custom folders to X2 in this as well.
4) Scan your plug-ins as usual, and you should be ready.
5) Open a session you know you have backed up elsewhere.
6) Fool around!  ...with X3. 
 
NOTE: I had to re-install my Waves plug-ins, but I used the same version, so I didn't have issues after that.
 
I personally found the process was painless. I'm also glad to say that my install didn't have the loud, obnoxious intro music this time. I didn't mind it at first, but when you're re-installing Sonar because something has gone bad, it's not a welcome thing.
 
I also had a major gripe regarding Take Lanes in X2, but this looks to be given a new existence in X3: Take Lanes! The way it's done in X3 is pretty well thought out. The gripes I had from X2 in Take Lanes is covered up by the new comping method, the new vertical scrolling, and the color coding you can do. I also like the comp'd result is what shows up in the Track! Even better than I would have thought.
 
So, for right now, moving to X3 was a hit. I've so far gotten my wishes (certainly not all of them) for what I deem most important for now and I can just keep working. Hopefully this opinion will not change. We'll see how the next recording session goes. Otherwise, I'm good for now!

+1 for a bug fix list or a X3 demo.  At the very least an ETA of when the demo will be out.
 
There are a number of bugs I have to have fixed before I will buy the X3 upgrade (I *really * want to!!).  I cannot tell if they are fixed without a demo or a list.  So I'm holding off.  Hopefully, any sweet upgrade deals from Melodyne, etc will be in effect when I can make sure X3 has had the fixes I need.
 
 

Or how about this one...dragging-and-dropping a properly formatted WAV file into an audio track results in said WAV file being placed somewhere far off in a distant galaxy within the track. Has that been fixed?
 
I believe in preferences you can uncheck the time stamp for importing audio . This should take care of the problem.
 
Danny

Glyn Barnes
That being the case its not a bug. It makes sense that time stamp audio clips are placed according to the time stamped unless you specify otherwise.

Awesome! A two-fer-one!
 
Well, it was a preference indeed. It's called "Always Import Broadcast Waves At Their Timestamp." I turned it OFF!  It works now, but talk about a cryptic preference setting!  Now WAV files can be drag-and-dropped into an audio track at the mouse cursor. Very good! Thanks!
 
...and...I did some experimenting just now with dragging and dropping MP3 files into an audio track. It appears that MP3 files that I have purchased from Amazon Music only give the error, while others work fine, either encoded from my CD collection or converted within iTunes from AAC to MP3. Something about Amazon's MP3-encoding process that Cakewalk does not like? Also, a sidenote--AAC files import OK as well. This helps me because I like to examine professional examples in RMIX and a spectrum analyzer.

The mp3 problem is because of embedded images as metadata as previously mentioned. You will need to open it up in an audio editor and then save it again stripping out the image/metadata. Then sonar can open it.

 I know this will sound weird but I once couldn't get one of those mp3s to load into Sonar so I renamed the extention from .mp3 to .wma and Sonar opened it!