The blueprint you linked here was superseded by another one.. here:
https://blueprints.launchpad.net/ubuntu/+spec/upgrading-running-software/
The original blueprint holds implementation ideas (tagging) and questions (will tagging apps require changes to Soyuz?), while the one superseding it suggests a brainstorming session.. did such a session happen? Was it documented by anyone?
Another more "Restart Required" specific spec lies here, created by Joel Ebel:
https://wiki.ubuntu.com/UpgradingRunningProgramsdoes Joel's spec somehow interfere with the changes you propose in your spec?
I think it is good to have multiple specs for the same cause, as long as we're brainstorming methods or as long as we're in draft stage.
For implementation, having rivalling specs within one project (Ubuntu) is either highly intentional or deadly to progress.
>...
>>> With the exception of Firefox updates, the old version works fine
>>> until restart. What you don't get is the benefit of the update.
>>> Firefox will stop working if not restarted (and warns about this).
>...
>> so then red is the wrong color
>
> Depends on what fix isn't in place. Leaving a remote root exploit in
> place seems pretty red to me.
>...
But you're no less secure, at that moment, than you were when Ubuntu
knew the update was available but you hadn't installed it yet. Should
the icon be red then too? And if not, why should it be red now?