Comment 11 for bug 844631

To clarify why I consider this bug Critical:

Our daily fast down-time is a great boost to the speed of getting new db-change-reliant features released. It has also got rid of that awful 90 minute window where parts of LP were down and other were read-only.

However, it has given us a user-experience regression in that we now present an OOPS rather than a friendlier "Hey, Launchpad is read-only but you can still do some stuff" message.

In my view:

 * an unexplained OOPS for up to five minutes a day, potentially every
day, just looks awful and I think it's safe to say that most people
seeing the OOPS won't have read the blog nor will they have found out
through our stakeholder process
 * Huw's new design brings in updates from the status feed and sends
people to subscribe to that, thereby making us appear more reliable in
future as they'll have had warning of such down-time.