info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Restoring MOVED resolution in bugzilla.mozilla.org
82 views
Skip to first unread message
Emma Humphries
Mar 27, 2018, 4:26:16 PM3/27/18
to fx-team, Firefox Dev, dev. planning, tool...@lists.mozilla.org
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
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
Kevin Brosnan
Mar 27, 2018, 4:26:17 PM3/27/18
to Emma Humphries, dev. planning, tool...@lists.mozilla.org, Firefox Dev, fx-team
Am I understanding the flow correctly?
Example bug: Summary: "Stylo Merge 2018-03-30" and when it is landed
in mozilla-central the bug is set to Status: resolved Resolution:
moved
The second part I am having trouble understanding the flow it is not
clear when someone (a bot?) should set the bmo bug to Status: resolved
Resolution: moved
> 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.
Moved makes me think we are moving bugs out of bugzilla not in.
Looking at history previous usage was moving bugs from bmo to an
internal Netscape tracker. I expected this announcement to be about
moving bugs that were filed in bmo first to GitHub. Has 'upstream'
been considered?
Kevin Brosnan
> _______________________________________________
> firefox-dev mailing list
> firef...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev
>
Example bug: Summary: "Stylo Merge 2018-03-30" and when it is landed
in mozilla-central the bug is set to Status: resolved Resolution:
moved
The second part I am having trouble understanding the flow it is not
clear when someone (a bot?) should set the bmo bug to Status: resolved
Resolution: moved
> 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.
Looking at history previous usage was moving bugs from bmo to an
internal Netscape tracker. I expected this announcement to be about
moving bugs that were filed in bmo first to GitHub. Has 'upstream'
been considered?
Kevin Brosnan
> firefox-dev mailing list
> firef...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev
>
Dylan Hardison
Apr 12, 2018, 10:48:01 AM4/12/18
to Emma Humphries, dev. planning, tool...@lists.mozilla.org, Firefox Dev, fx-team
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.
Especially not good to do this right after the big migration.
Dylan Hardison
Apr 12, 2018, 10:48:01 AM4/12/18
to Emma Humphries, dev. planning, tool...@lists.mozilla.org, Firefox Dev, fx-team
Just a brief update -- MOVED is enabled on *bugzilla-dev* and will be enabled on production
as soon as we do a brief bit of QA; it's not likely to break anything. I suspect it will re-re-return
UTC April 12th unless we find something that doesn't expect new resolutions to be added.
Note this is a concern not for BMO, but for infrastructure that talks to bmo, including phabricator.
As far as BMO is concerned, you can have bug status called RUN and a resolution of AWAY, and "resolve" bugs as RUN AWAY.
as soon as we do a brief bit of QA; it's not likely to break anything. I suspect it will re-re-return
UTC April 12th unless we find something that doesn't expect new resolutions to be added.
Note this is a concern not for BMO, but for infrastructure that talks to bmo, including phabricator.
As far as BMO is concerned, you can have bug status called RUN and a resolution of AWAY, and "resolve" bugs as RUN AWAY.
0 new messages