1379541 - Release standalone ESR52 SpiderMonkey tarball

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect, P5)

Description

[Philip Chimento [:ptomato]]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce:

Downstream packagers need a "blessed" standalone release tarball of SpiderMonkey 52. (Ideally this release would be cut after backporting fixes for all the issues I've found with building SpiderMonkey standalone.)


Actual results:

SpiderMonkey standalone tarballs can be had from Treeherder, but it's very non-obvious to outsiders how to get them, and it's not clear whether the download links are permanent (are they?)


Expected results:

Available from a page similar to https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Releases/45

Comment 1

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals

Comment 2

[Philip Chimento [:ptomato]]

Bug 1176787 is closed now, but there isn't a fix for ESR52. Downstream I am using this patch [1], but it looks like that is not acceptable for backporting to ESR52. I would suggest to go ahead and release a tarball after fixing the one remaining blocker, and make a note that embedders will have to patch it; or somehow get the tarball generation script to apply my patch to the tarball.

[1] https://github.com/ptomato/mozjs/commit/89eb9770792107d0d9b0b5c745abe59868d36903

Comment 3

[Philip Chimento [:ptomato]]

Is releasing an official tarball of ESR52 likely at this point, or should we just close this?

Comment 4

[Nicolas B. Pierron [:nbp — off until 29-09]]

I think Steve might have an answer to the question in comment 3.

Comment 5

[Sylvestre Ledru [:Sylvestre]]

As we killed esr52, I think we can close it