launchpad-dev team mailing list archive

[Robert Collins <robert.collins@xxxxxxxxxxxxx>]

On Tue, Oct 12, 2010 at 7:54 AM, Edwin Grubbs
<edwin.grubbs@xxxxxxxxxxxxx> wrote:
> Bug 427263 (Impossible to edit bug descriptions with Konqueror) is
> currently tagged qa-bad. Does this need to be added to
> https://dev.launchpad.net/CurrentRolloutBlockers ?

https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
and
https://devpad.canonical.com/~lpqateam/qa_reports/deployment-db-stable.html

are both authoritative for deployments these days; we can't deploy
anything at the moment - we're stalled on QA.

> We still have several bugs that need to be QA'ed. Since staging is
> currently unavailable due to problems updating the db (see Tom
> Haddon's email), I have split up the bugs that can be QA'ed now on
> EDGE versus those that will have to wait until staging is working.
>
> Bugs that can be QA'ed on EDGE
> ------------------------------------------------------------------------
>    645403 TooNewRecipeFormat raised editing a recipe
>        ON EDGE ~rockstar/launchpad/recipe-too-new
>             merged into ~launchpad-pqm/launchpad/devel at rev 11612

This is one of them :)

>    645702 oops in holdMessage storing large message
>        ON EDGE ~sinzui/launchpad/hold-message
>             merged into ~launchpad-pqm/launchpad/devel at rev 11685
>
>    652626 Windmill egg needs to be upgraded to fix test breakages
>        ON EDGE ~wallyworld/launchpad/windmill-1.3r1544
>             merged into ~launchpad-pqm/launchpad/devel at rev 11684

This doesn't have any bearing on deployment, I'll mark it ok (because
the test suite which it affects is working).

>    627701 Make it possible to use feature flags to override the
> global timeout for specific pages
>        ON EDGE ~matsubara/launchpad/fix-bug-627701-override-global-timeout
>
>        ON EDGE ~lifeless/launchpad/bug-627701
>             merged into ~launchpad-pqm/launchpad/devel at rev 11668

This cannot be QA'ed on edge. (The way to QA it is to drop the timeout
way low, or way high on a page that times out) - both will have
negative impact on our users).

-Rob