-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11-12-14 12:30 PM, curtis Hovey wrote: > I think we have a simpler set of rules based on Francis posting > that helps us to prioritise work. Fallout and regression bugs are > criticals because we recently made something worse for users.
Fallout can be a regression, but when it's not, we haven't made something worse for users. They couldn't do it at all, now they can do it, but it's buggy. We have, however, made the codebase more buggy. > These bug queue must be kept at zero. Agreed, but because we must not let the codebase become more buggy. > The rules for setting importance based on tags and the team that > is driving the queue to zero look like this: > > Feature team Maintenance team | CRITICAL fallout | escalated > regression | regression blocker | blocker | HIGH <feature-tag> | > oops | timeout I don't understand what this means. If you mean that maintenance teams would not work on fallout bugs, I don't think that's right, because fallout can be discovered after the feature is completed and the team rotates. Whatever team is on maintenance should fix fallout if it's discovered after feature completion. Maybe we can just use tags? That way we wouldn't have to change the bug importances to reflect them. Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7o7UoACgkQ0F+nu1YWqI0J8QCeJdNxMI8hcxWa4f2yip/1OxCT JpMAmwckkz64/Yl1/oVYjwRAy5/bQ1Jq =5zHv -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
