It's a bit awkward, but to generate a page needed to update
BoostPages_Page, which wasn't always appropriate. So now generate pages
just using the data from the quickbook source, combined with the state
data.
So that they don't overwrite the beta release notes. This means that
there's no way to update the beta release notes, but I guess that can be
done manually.
I'm going to create a new page for 'in progress' release notes, and only
write the release notes pages for actual release (including beta
releases). That way the beta release notes can be left in place while
the release notes are updated for the next beta/full release. Changes to
the release notes after the final release will be updated.
Main change is that 'unversioned.qbk' now has null release_data. Will
result in a change to the qbk_hash, but I'll manually handle that. This
means that its no longer a 'release' but still want it to appear on
history page.
I didn't want to use the existing mustache, as I want to keep the site
dependency free for now, and not have to deal with caching compiled
templates. Might switch to using composer on the site in the future.
This isn't full mustache syntax, and might behave slightly differently?