Restoring MOVED resolution in bugzilla.mozilla.org
Emma Humphries <[email protected]> Mon, 26 Mar 2018 18:01:41 -0700
| Newsgroups | gmane.comp.mozilla.firefox.devel,gmane.comp.mozilla.devel.seamonkey |
|---|---|
| Message-ID | <CAL_vYcpPGX=GYzgyn2xXD2ZZ02ZE3+H5O47ge6J8SgB0RUT1VQ@mail.gmail.com> |
--===============0894990095310352879== Content-Type: multipart/alternative; boundary="f4f5e80c7da069bab305685a71c7" --f4f5e80c7da069bab305685a71c7 Content-Type: text/plain; charset="UTF-8" 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 --f4f5e80c7da069bab305685a71c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he= lvetica,sans-serif">In the past we had a MOVED resolution for bugs which we= stopped using. <br></div><div class=3D"gmail_default" style=3D"font-family= :arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style= =3D"font-family:arial,helvetica,sans-serif">Given the number of pieces of F= irefox being built in GitHub and other systems which may be using their own= bug trackers, it is worthwhile to allow that resolution. <br></div><div cl= ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br>= </div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san= s-serif">If your part of the project creates a BMO tracking bug for bugs yo= u track internally, don't use this resolution, resolve the bug as you w= ould normally. <br></div><div class=3D"gmail_default" style=3D"font-family:= arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D= "font-family:arial,helvetica,sans-serif">If your project lands code in Mozi= lla-Central under a separate merge ticket in BMO, but individual bugs are t= racked in your own bug tracker, use this resolution and in the See Also fie= ld put a link to the successor bug. <br></div><div class=3D"gmail_default" = style=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gm= ail_default" style=3D"font-family:arial,helvetica,sans-serif">If your proje= ct 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.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica= ,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:ar= ial,helvetica,sans-serif">I'll leave this discussion open through Frida= y, the 30th, and if there's no substantive changes warranted, I'll = enable MOVED as a resolution on Monday, April 2nd, start tracking bugs reso= lved MOVED that don't point to a ticket on another issue tracker using = the See Also field.</div><div class=3D"gmail_default" style=3D"font-family:= arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D= "font-family:arial,helvetica,sans-serif">-- Emma<br></div></div> --f4f5e80c7da069bab305685a71c7-- --===============0894990095310352879== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/firefox-dev --===============0894990095310352879==--