Our spidermonkey release notes are a mess. I have a script to generate API deltas with associated bug numbers, which helps a tiny bit, but it would be much more robust if we had requirements around release notes that were enforced via hg hooks. Specifically, Terrence and I discussed something like: - use moz.build files to identify all exported headers - changes to the headers require corresponding changes to some sort of in-tree ReleaseNotes.txt file - with a simple opt-out mechanism in the commit messages - this should? should not? include mfbt/ as well