1465547 - Update Debugger Frontend v61

Status: RESOLVED FIXED

(DevTools :: Debugger, enhancement, P3)

Description

[David Walsh :davidwalsh]

https://github.com/devtools-html/debugger.html/compare/release-60...release-61

Comment 1

[David Walsh :davidwalsh]

Try:  https://treeherder.mozilla.org/#/jobs?repo=try&revision=7247c66ad1cc51095508760359a7322566e8a56c

Comment 2

[David Walsh :davidwalsh]

Attachment: Release61-1.patch

My first attempt at a real release -- be kind jdescottes!

Comment 3

[Julian Descottes [:jdescottes]]

Comment on attachment 8981977 [details] [diff] [review]
Release61-1.patch

Review of attachment 8981977 [details] [diff] [review]:
-----------------------------------------------------------------

Very nice! Try is exceptionally green. Quick manual test looks ok. Didn't see anything weird in the updated files. 

Talos push: https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=a59ffab9d35192207b99cdef949b37ad9a96257e&newProject=try&newRevision=27edb93f822a0c248082ddce553a70c4608db53e&framework=1

One comment about the GitHub side of things. 
Usually Jason includes a last commit when doing a release which updates assets/module-manifest.json. The commit is named after the release number (here it would be "Release 61"). 
Now that we no longer bundle the debugger though, I'm not sure we should keep doing this?

Jason: can you give your input about this, do you feel like this additional commit is still needed?

Comment 4

[Jason Laster [:jlast]]

yep, we should still have it for the other bundles.

the steps are:
1. yarn copy
2. git add .; git commit -m 'release N'

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/335af54ff2cb
Update Debugger Frontend v61 r=jdescottes

Comment 6

[David Walsh :davidwalsh]

I've added the update to assets/module-manifest.json and updated the branch on GitHub.

Comment 7

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/335af54ff2cb