The issue is that AC RELEASES BUGGY SOFTWARE....
Why don't they test adequately before release?
One of the things I learned at the clinical advisory board meeting last week is that AC knows this. They recognize that unplanned, patch releases were frequently needed. In fact, they are making major efforts to address this and perform appropriate testing before a new release. They are working toward a schedule of quarterly, reliable releases with less need for "emergency fixes".
In the post-Pri-Med period, AC has created an entire quality assurance department and has hired a number of engineers to test new releases. You can imagine that it is a challenge to retest every aspect of the program when changes are made. Keep in mind that the program has hundreds of interacting features (many of which most of us don't regularly-or ever- use). When the product is released, it is used on hundreds of differing network configurations with different OS's, hardware, wired/wireless set-ups, etc.
So testing is not a trivial or quick proposition, especially since everyone wants new features and fixes, and they want them delivered promptly. What they have done is invest in more QA people AND create and expand an automated testing process. This vastly accelerates testing and makes much more comprehensive testing possible in a shorter time interval. They believe that this is already significantly reducing the number of bugs and broken features in new releases.
Time will tell, but this is an area in which they are acutely aware of the problem and have taken major steps to address it, in my opinion.
As Donna says, I don't use any other software where I wait until I hear about it for two months to install it.
So how is Windows 10 running in the office for you guys?
