There no support for release candidates yet, as we've never put them on
the site before. Will just treat it as the final release details to see
how well it works.
Won't acheive much, as I don't think they do a good job of returning
error values, but can work on that. Using an old version of quickbook,
but I thin that's okay.
I think I'll use this in a cron job, so that updates to more public
pages can be checked before being released. Also won't have to deal with
automatically adding new files.
It doesn't include all the data the is currently stored, there's some
code that attempts to work round that, but it generates incomplete pages
because some of the data is missing. So better just to clear the cache.
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 it doesn't update the state in ways that we don't wish it to. A
little awkward as it can update a page that isn't in the cache without
recording it as updated.
Moved the logic for handling beta pages into convert_quickbook_pages as
it didn't make much sense in load_quickbook_page. Also simplified a bit
as there should always be a cached entry for a beta page. Perhaps should
store the beta pages in a separate file?
To fix the bug where the development release notes didn't have all the
appropriate data.
I might not do this, I feel like it might be better to create a new
'section'.
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.
