Mozart Life Cycle

Our policy on Mozart's life cycle in relation to Microsoft's "Windows as a Service"

 

Mozart Life Cycle Support

Context

In the past it was sufficient to say that such-and-such a program runs on Windows XYZ. If a certain program ran on a certain version of Windows, that was that.

With Windows 10, however, Microsoft have introduced a new distribution model, "Windows as a Service", which boils down to delivering regular (minor and major) updates to the Windows 10 operating system. The statement "This program runs on Windows 10" therefore carries an implication that it should go on running on Windows 10 after the next Windows 10 update. To ensure that this is true the originator of the program must have a policy on maintaining compatibility, as and when it becomes necessary. This page defines our policy on Mozart's life cycle.

Mozart's Life Cycle

Since Mozart's first release in 1994, updates have fallen into two categories: "new major versions" and "service packs". New major versions have appeared at intervals roughly of 1 to 3 years at a discount price to users of any earlier version. Free Service Packs for the current major version have appeared typically at intervals of 1 to 3 months, as and when any problems have been revealed. This policy will continue in the current era of "Windows as a Service" - where Microsoft release regular updates to Windows 10.

Our 'programming policy' has always been, and will continue to be, 'conservative': focusing on the well documentated established interface with Windows, with the result that just about all changes to the Operating System as it has evolved, have left Mozart unaffected. Our second line of defence, should any problems of this nature occur, is the prompt issue of a free Service Pack for the current major version, and this policy will also continue.