[Update] Revert RESOLVED:INACTIVE State

[Erin Lancaster]

Here’s where we are with timing/process for the revert:

Friday May 25th => Monday 28th
Revert Script Testing+ Adding Exceptions

1) As Dave mentioned, this is the place to comment and request any special cases you want the script to make: https://bugzilla.mozilla.org/show_bug.cgi?id=1464312 <https://bugzilla.mozilla.org/show_bug.cgi?id=1464312> (so far we have exceptions for kmag, marco). It would be helpful to have these requests before end of day Monday or as early as possible Tuesday.
2) Once we think we have a complete list of exceptions and they are made in the script, the changes will be reviewed, and dylan + dkl will verify the data is correct on the staging DB.

Tuesday May 29th
Revert Starts/Target Revert Completion

3) A message will be sent to inform everyone the revert process will begin (starting with most recent bug IDs). We are targeting Tuesday morning ET.
4) This will take way more than 6 hours to complete; a message will be sent letting people know once the revert is done.

I hope this plan is copacetic. Questions and feedback are welcome.

Thank you,
Erin


> On May 25, 2018, at 12:23 PM, Dave Camp <dc...@mozilla.com> wrote:
>
> Yesterday a mass change was applied to bugzilla to move a set of bugs to a RESOLVED: INACTIVE state.
>
> Dealing with inactive bug reports has been a contentious issue in the past. While I think it’s time for us to revisit that issue and make different choices than we have in the past, a change of this magnitude shouldn’t have been applied to the live bugzilla database before sufficient discussion happened. The decisions about what constituted an active bug, how that categorization should be reflected in the database, and whether different subsets of bugs need different policies were not discussed.
>
> Therefore, we will reverse this change. We are testing the script in https://bugzilla.mozilla.org/show_bug.cgi?id=1464312 <https://bugzilla.mozilla.org/show_bug.cgi?id=1464312> to make sure the revert goes well and once we have confidence that the script is working as expected a note will be sent to confirm the timing.
>
> To address some of the questions that have come up:
>
> Q: What will happen to the bugs that were moved to INACTIVE and then re-opened?
> A: If the last change to a bug was NOT the automated change to INACTIVE, then nothing will happen to the bug when the reversion script is run.
>
> Q: What constitutes a last change?
> A: *Any* modification to a ticket. If there are bugs you wanted to revert and were not, we’ll work with you to fix it. Respond to this thread and we will address the problem.
>
> Q: What will happen if I re-triaged bugs that were moved and decided to leave a subset of them Closed:Inactive?
> A: Place a comment in https://bugzilla.mozilla.org/show_bug.cgi?id=1464312 <https://bugzilla.mozilla.org/show_bug.cgi?id=1464312> to request that your bugs are left alone.
>
> Q: Will bugmail be sent as a result of the revert?
> A: No.
>
> Q: What will happen to the last modified date?
> A: Reverting will restore the last modified date.
>
> Q: How long with the revert process take?
> A: Once it is kicked off, it should take hours to complete. An email will be sent once it starts and a notice once it is complete.
>
> We recognize that this move impacted a lot of people, and we don’t want to make things worse. We’re trying to make this happen as quickly as possible, but we want to take enough time to make sure it happens as smoothly as possible. Thank you for your patience while we work this out.
>
> Thanks,
> -dave

[Boris Zbarsky]

On 5/25/18 5:07 PM, Erin Lancaster wrote:
> Here’s where we are with timing/process for the revert:

Erin,

Thank you for all the work you've put in on this. I know it hasn't been
easy dealing with this, and I really appreciate it.

-Boris

[Erin Lancaster]

Of course, happy to get us back to a good place and very sorry for all of
the inconvenience. We haven't had any further requests for exclusions for
the revert: https://bugzilla.mozilla.org/show_bug.cgi?id=1464312. It would
be helpful to get any other requests in asap.

Dylan will be checking the ticket first thing Tuesday morning ET and will
then get going with final review/testing. Many thanks to Dylan and to Mark
for all their support.

Erin

[Dylan Hardison]

The process has begun. We'll send out another announcement when it is done (or if there are issues).

> _______________________________________________
> firefox-dev mailing list
> firef...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev

[Mark Côté]

The process finished this morning. The vast majority of bugs were successfully reverted. As intended, some were skipped due to having been updated since the first script ran. There were also a handful of unexpected errors that we will be cleaning up manually. See https://bug1465190.bmoattachments.org/attachment.cgi?id=8981848 for the full results and https://bugzilla.mozilla.org/show_bug.cgi?id=1464312 for discussion.

Mark