Closed Bug 1610077 Opened 4 years ago Closed 4 years ago

Move Core:WebReplay to graveyard

Categories

(bugzilla.mozilla.org :: Graveyard Tasks, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: emceeaich, Assigned: dkl)

References

Details

Personally, what I'd like to see here before the component gets removed is that we get the removal landed, then I want to wait a few days and go through all of the outstanding crash bugs in the component. I can't imagine how they'd persist past the removal (and they've probably gone away already if nobody is actually using WebReplay), but it'd be good to check. I'm happy to do that.

I found some followup removal that can be done, but those bugs can be filed in the components for the places where the code is being removed.

(In reply to Andrew McCreight [:mccr8] from comment #1)

Personally, what I'd like to see here before the component gets removed is that we get the removal landed, then I want to wait a few days and go through all of the outstanding crash bugs in the component. I can't imagine how they'd persist past the removal (and they've probably gone away already if nobody is actually using WebReplay), but it'd be good to check. I'm happy to do that.

I found some followup removal that can be done, but those bugs can be filed in the components for the places where the code is being removed.

Let me know when I need to move this component to graveyard.

Flags: needinfo?(continuation)
Flags: needinfo?(continuation)

I've gone through all of the open WebReplay bugs that are intermittent failures or are crashes with signatures and closed them after confirming that they weren't happening any more. (I moved one intermittent failure out of the component.) The actual removal still needs to be finished up, though.

I think it is okay to move Web Replay to the graveyard now. Thanks. No hurry, of course.

Flags: needinfo?(dkl)

Component moved to graveyard.

Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(dkl)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.