Re: Restoring MOVED resolution in bugzilla.mozilla.org
Dylan Hardison <[email protected]> Wed, 11 Apr 2018 11:46:27 -0400
| Newsgroups | gmane.comp.mozilla.firefox.devel,gmane.comp.mozilla.devel.seamonkey |
|---|---|
| Message-ID | <[email protected]> |
Sorry I didn't chime in until after the fact, but it's not acceptable to have this on yet without testing / QA. Especially not good to do this right after the big migration. > On Mar 26, 2018, at 21:01, Emma Humphries <[email protected]> wrote: > > In the past we had a MOVED resolution for bugs which we stopped using. > > Given the number of pieces of Firefox being built in GitHub and other systems which may be using their own bug trackers, it is worthwhile to allow that resolution. > > If your part of the project creates a BMO tracking bug for bugs you track internally, don't use this resolution, resolve the bug as you would normally. > > If your project lands code in Mozilla-Central under a separate merge ticket in BMO, but individual bugs are tracked in your own bug tracker, use this resolution and in the See Also field put a link to the successor bug. > > If your project does not land code in Mozilla-Central, and you use your own bug tracker, use this resolution and in the See Also field put a link to the successor bug. > > I'll leave this discussion open through Friday, the 30th, and if there's no substantive changes warranted, I'll enable MOVED as a resolution on Monday, April 2nd, start tracking bugs resolved MOVED that don't point to a ticket on another issue tracker using the See Also field. > > -- Emma