I've been occasionally working on a tool to compare the header files between two versions of js/ to describe the differences between them. The goal is to have something that (1) serves as a decent starting point for release notes, and (2) can be rerun with manual edits for incremental updates. I also want it to use revision control to autodetect which bug added/removed each API call. (I haven't implemented that part yet in this version; I have an older tool that does this already, with limitations, but I'm switching from Perl -> Python3 so I'm redoing it all.) It tries to be fancy and detect when things move between files, get moved from JS_Foo to JS::Foo, etc. It doesn't parse eg the release notes page on the wiki or anything; I haven't decided what the canonical source of truth should be. This tool should not block any release. People would much rather have the release than wait on slightly better release notes. I'm just filing a bug to have something to hang the current state off of.