Comment 19 for bug 331054

We've built a more consistent model of how applications should lead
users to be aware of decisions they need to take. Updates are important
decisions, we need to catalyse a decision. We don't need to completely
interrupt the workflow, but we need to put this decision "into the queue".

Rather than putting up a persistent indicator, as we did in the past, we
want to lead the user directly to the place they can take action.

There are four ways an app can raise awareness of an event, state, or
decision. It can notify, with a temporary hint. In certain cases, it can
also ask the system to put up a persistent indicator. In other cases, it
can open a window in the background queuing the decision, and in the
most extreme cases it can grab the focus with a system modal dialog.
There are clear guidelines for deciding when an app should use each of
those approaches, or combinations of them. In this case, update-manager
should be opening a window in the background.

Mark