Re: Firmware 4.5.2 QC35 ii
>The reason why we no longer allow back-peddling of firmware versions of our products is because we have seen cases where installing older versions of firmware has created unexpected behaviour in a product and negatively impacted or reduced
With all due respect, this is not really what users are asking for. They are not asking to go back to some random version. They are asking for the same feature that has been designed into the installation routines for the Microsoft Windows environment for the last 20 years. If you start with firmware A and have a problem with firmware B, then all they are asking is for an immediate installation undo back to what the environment looked like prior to the upgrade - version A. It is hard for me to believe that going back to what the QC35ii looked like 20 minutes ago or even two hours ago could create any unexpected behavior anymore than it would have without doing the installation at all. Your explanation could make sense in some general context but for an installation scenario is not imho accurate.
The users are not looking to do a unauthorized upgrade/downgrade or even to do a downgrade as the process you had last year. What they are asking Bose is to modify the installation process to hold on to what everything looked like before the installation and then after the installation ask whether to keep the installation or go back to the way it was before the installation started.
This practice is still universally done in the laptop/desktop world. For example, it very common to update say a display driver and then the installation asks at the end if everything went OK and if you answer No, it puts things back. Simply, that is all that is being asked for - give the user a way to UNDO and installation at the end of the process - not next day, not next week, not two versions back.... a simple UNDO.