A fix log, while good sounding, isn't always a great indicator between version cycles. There's a few reasons for this:

1) Some things get fixed without their reports getting closed. This has to do with the fact that sometimes when you fix something or implement a new feature you inadvertently fix other things. It's not until you backtrack and go through the logs on downtime that you'll find it fixed and can close it out.
2) We get duplicate reports either from the Beta team, end users, or internally. Sometimes we'll close out something a few times. On the face of it you'll see 5 fixes, but it was really 1.
3) Sometimes things change so much the old issues will simply not exist anymore.
4) Sometimes devs find and fix things before they are ever logged.
5) There's usually some pretty bad issues in development, like CRASH CRASH CRASH. Since the user never sees this there's not much need to report it. If anything it may cause more alarm and give 'ammo' to trolls.
 
As you can see there's lots that are at play. I believe there was around 100 customer reported or talked about issues fixed this cycle. Though I suspect that number is actually higher. I think we'll be able to get lists out in point releases though as that's a bit more manageable.
 

cclarry

backwoods
That's even faster than Steinberg updates. Shows they care right 

or they goofed....one or the other...hopefully the former and not the later...

 
Nope, we just wanted to keep busy and continue to improve the product. If you don't set a deadline for something nothing gets accomplished.

In other words only installed users will actually know what has been fixed for now (if they know what they are looking for)?
 
I was a VP of Software Developemnt for a highly complex ERP system for five years. We had a bug tracking system in 1982 that told customers by tracking number what bug had been fixed and published it when we delivered a major or minor release.
 
I'm pretty sure no one want to see anything from CW's #5 as that is ONLY development rated. But really, with all due respect, your explanation of being unable to tell the customer base what was fixed is straight out of the 1960s unless your tracking system is entirely paper based and then I'd say the 1940s.
 
Nuff said. I will not harp on this.

bapu
In other words only installed users will actually know what has been fixed for now (if they know what they are looking for)?
 
I was a VP of Software Developemnt for a highly complex ERP system for five years. We had a bug tracking system in 1982 that told customers by tracking number what bug had been fixed and published it when we delivered a major or minor release.
 
I'm pretty sure no one want to see anything from CW's #5 as that is ONLY development rated. But really, with all due respect, your explanation of being unable to tell the customer base what was fixed is straight out of the 1960s unless your tracking system is entirely paper based and then I'd say the 1940s.
 
Nuff said. I will not harp on this.

The CWBRN public system is separate from our internal system. I think Ryan has mentioned this multiple times. This is to keep out junk reports and 'Contact Supports' out of the dev system.

Seth Kellogg [Cakewalk]
If anything it may cause more alarm and give 'ammo' to trolls. 


If you don't set a deadline for something nothing gets accomplished.

The trolls will make up their own ammo!!

And yes you have to set up deadlines for things to progress.

Have read the promos and am very anxious to get with it. So far ya'll are doing a great job on this roll out!!

And it shows you have listened.

+1 to the OP and Billy Buck.  I'll be making my buy decision based not on the obvious VST3 changes and added plugs, but on improvements and fixes for all the more subtle workflow issues.  Need the list.  Make that +3.

Grem

Seth Kellogg [Cakewalk]
If anything it may cause more alarm and give 'ammo' to trolls. 


If you don't set a deadline for something nothing gets accomplished.

The trolls will make up their own ammo!!

And yes you have to set up deadlines for things to progress.

Have read the promos and am very anxious to get with it. So far ya'll are doing a great job on this roll out!!

And it shows you have listened.

+1

noels blog goes some way towards discussing such horrors as bugs fixed :-)

+1 for complete changelog and bug fix list.
 
If available somewhere in the installer suite, please post here.

Completely agree. 
 
I honestly would have considered paying for a pure bug fix/maintenance release to X2.  I cannot, however, jump to a new version with new bugs when the previous version was abandoned since 2012.
 
Not every update needs to be a marketing extravaganza.  The product needs bare bones maintenance every release.  The experience with X2 this year was off-putting to say the least.

Perhaps we all should launch X3 and push it to the limits and see what happens.  What better way to determine if it performs?  Those of us who had problems in X2 could open a project that gave us problems and judge from there.  Don't forget to save it with a different name.  Always safe to do that.  Those who are waiting to see how X3 performs keep watching and the 411 will unfold right before your eyes and you can buy or not.  Let's make some music.  Got a problem write a song about!  "Do Worry Be Happy!"