Put the main bug marking phase/step after the others

Issue #12 resolved
Ed Morley
created an issue

At the moment, I tend to move forwards a step or two before marking bugs, to check the "things that were backed out, but not part of the merge" and "other changesets" steps haven't mis-identified anything. I then have to go back to step one and submit the bugs. If we moved the bug marking step later, one could be sure that any tweaks (eg due to someone mangling the backout message so it not getting paired up with the right changeset) can be made before bugs are marked - thereby saving closing a bug and having to reopen manually at a later step.

Comments (3)

  1. Log in to comment