- run autoconf213 in js/src so that we ship a working "configure"
- steps related to Makefile.ref, js.mak, etc elided
- I have not updated the change log. Is this really necessary? Is there a non-manual way to do this? There were ... several ... changes made between 1.7.0 and 1.8.5
- Obviously, CVS tagging no longer applies. How about we tag the hg rev we push with bug 586016?
- Tar now has one more top-level directory -- this is to allow us to ship things like NSPR and jemalloc later if we want to in the same tar ball
- README moved to higher level dir
Also.... Can I please, please change "libmozjs.so" to a better name in the tar release? How about libmozjs185.so.1.0.0? I think this would help the distro use-case, and make it possible to ship bug fixes on top of JS-1.8.5-the-language -- while properly advertising API/ABI compatibility. And, of course, making room for JS-1.8.6-the-language.
I would like to release a JS 1.8.5 tar ball ~ concurrently with Firefox 4.
Here is a sample tar-ball and browseable tree based on a snapshot of today's tracemonkey repo: http:// www.page. ca/~wes/ js-releng/
Some notes where I've differed from the existing release process at http:// www.mozilla. org/js/ spidermonkey/ release- notes/spidermon key-releases. html:
- run autoconf213 in js/src so that we ship a working "configure"
- steps related to Makefile.ref, js.mak, etc elided
- I have not updated the change log. Is this really necessary? Is there a non-manual way to do this? There were ... several ... changes made between 1.7.0 and 1.8.5
- Obviously, CVS tagging no longer applies. How about we tag the hg rev we push with bug 586016?
- Tar now has one more top-level directory -- this is to allow us to ship things like NSPR and jemalloc later if we want to in the same tar ball
- README moved to higher level dir
Also.... Can I please, please change "libmozjs.so" to a better name in the tar release? How about libmozjs185. so.1.0. 0? I think this would help the distro use-case, and make it possible to ship bug fixes on top of JS-1.8. 5-the-language -- while properly advertising API/ABI compatibility. And, of course, making room for JS-1.8. 6-the-language.