Its probably incorrect to assume the didn't know about this proir to release.  They probably have hundreds of open tickets.  Release dates don't slip, minor bugs get pushed out. This is a backwards compat issue which will not affect new projects and over time there will be less occurances of it.  They may work it off but its low priority.  Small market share in sonar. They address visible issues for larger platforms first.
 

Hm, I am not sure this will not affect new projects.  And I question the statement that Sonar users upgrading from version 1 is a small group; however, I don't really have the data to know.

I am a software engineer for many years and towards a release there are a ton of bugs, there is no way to fix all of them.  My point is that rather than delay release, they will focus on the big issues.  Fix the highly visible/easy bugs, delay the less visible/difficult bugs.  The kinds of bugs that the user community is finding will give you an idea of how mature the product is upon release.
 
The EZD2 "incompatible with old projects in Sonar" seems like a moderately low visibility, high difficulty fix and may require collaboration with Cakewalk.  This doesnt mean they didn't know about it before release.  Its not because they "didn't test" or "don't care about Sonar", its more likely that they were pushing the deadline.

[Deleted post, not because I said anything bad, rather it didn't contribute, commenting that I'm laughing my ass off does not add to any constructive conversation].

Sonar doesn't have the ability to swap the number of outs dynamically, no?

CakeAlexS, Share the joke with us because this whole thing has not been funny to me.  I could use some humor.

I have an feeling i get whatever Alex wrote.........., for once.

Personally :

I insert EZ2 as a soft synth, multiple outputs
I move/slide the midi data from the EZ1 folder to the EZ 2 folder and change its target to the EZ2 engine.
I delete the EZ1 folder
I select my EZ2 kit and if neçessary re-assign outputs, as and when i want to
I make music.
Where is the show stopping problem ?

Its a "hassle" sure, but a few clicks.....

Cheers,
Jerry

joakes
I have an feeling i get whatever Alex wrote.........., for once.

Personally :

I insert EZ2 as a soft synth, multiple outputs
I move/slide the midi data from the EZ1 folder to the EZ 2 folder and change its target to the EZ2 engine.
I delete the EZ1 folder
I select my EZ2 kit and if neçessary re-assign outputs, as and when i want to
I make music.
Where is the show stopping problem ?

Its a "hassle" sure, but a few clicks.....

Cheers,
Jerry

I am not sure how this helps people who have projects started with EZD1 who have installed EZD2.
 
Perhaps I have missed something.
 
Since Alex has deleted his post, it is always possible that I have.
 
The EZD2 issue has cost me a lot of hassle and time.  I guess I missed the joke..

scook
I believe that link was posted in #2  above

CakeAlexS
I believe that link was posted in #2  above

Yes but in POST #3 the OP says it did not work, without a detailed explanation, and I was pointing it out again in case he did not try the exact scenario.


 
My bad.
 
Or Deja BaVu!

joakes
I have an feeling i get whatever Alex wrote.........., for once.

Personally :

I insert EZ2 as a soft synth, multiple outputs
I move/slide the midi data from the EZ1 folder to the EZ 2 folder and change its target to the EZ2 engine.
I delete the EZ1 folder
I select my EZ2 kit and if neçessary re-assign outputs, as and when i want to
I make music.
Where is the show stopping problem ?

Its a "hassle" sure, but a few clicks.....

Cheers,
Jerry

Thank you very much.  This is sort of my point.