Comment 26 for bug 332945

Brian:

Yes, I think that's the main problem. According the spec, update-manager should be a morphing window by the time this piece of work is "finished", right? That will solve pretty much all of the problems relating to it becoming a pop-up, I believe. I expect we'll end up needing to file a few usability bugs to get it all sorted and user-friendly - for instance, it's not currently a morphing window and if a partial upgrade is needed, it pops up a *focussed* window. If these aren't currently being sorted, they should be bugs... but they're not as important as the loss of passive information in *this* bug.

The basic regression, then, is thus:

1) No *continuous* reminder that a reboot or log-out is necessary. A pop-up window is a terrible thing for this: If it can't be closed, it's a constant annoyance. If it can, it's not continuous!
2) No policy for what happens if the user closes the update-manager window after it pops up. Do we really want to leave them a day (presumably) when there are security updates? Or another week if there are upgrades? The lack of some continuous reminder is a regression.

There are other issues with the *current state* of the new system which should be split out into new bugs - but those aren't regressions.