Closed
Bug 749982
Opened 13 years ago
Closed 11 years ago
Create JS 1.8.8 source release
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Waldo, Unassigned)
References
()
Details
+++ This bug was initially created as a clone of Bug #735599 +++
I need a placeholder bug, and version number, to be able to start documenting SpiderMonkey work that happened after the Firefox 10 release, and after the JS1.8.7 release, for whatever the next release will be. :-) The version number I'm mentioning here is just a placeholder -- I don't know if we want it to be that, or something else (like, say, the corresponding Firefox version number).
Initial release notes (note that people making changes to SpiderMonkey should be updating this doc as necessary to document their stuff):
https://developer.mozilla.org/en/SpiderMonkey/1.8.8
If I missed CCing anyone making changes to SpiderMonkey as concerns embedders, or as concerns SpiderMonkey release notes, please add 'em. :-)
Reporter | ||
Updated•13 years ago
|
Comment 1•12 years ago
|
||
For those wishing to start testing, I have put together a basic archive based on fx-17.0.2 release code. I have included a fix/workaround for mv -f bug issues seen in gentoo/openbsd. I have also included
moz188-fix-version.patch
moz188-install-headers.patch
moz188-libname-changes.patch
libname changes is almost identical other then change for mv -f failures. Please find a test archive @
http://dev.gentoo.org/~anarchy/dist/js188-1.0.0.tar.xz Any bugs please let me know as soon as possible I would like to get this moving along. It is way over due.
A couple of related bugs, which should hopefully get landed upstream, before release.
https://bugzilla.mozilla.org/show_bug.cgi?id=831552
https://bugzilla.mozilla.org/show_bug.cgi?id=812265
Reporter | ||
Comment 3•11 years ago
|
||
The JS17 release obsoleted this, or something.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Keywords: dev-doc-needed
You need to log in
before you can comment on or make changes to this bug.
Description
•