I was thinking about resolving this by removing the release data for
bjam, but instead support different release names. Even though this is
currently just for one special case, might be useful in the future.
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.
Previously was using the quickbook file's pub_date, By using the date
the release script was run on, can release without updating the
quickbook file. So the release manger won't need to have quickbook
installed. At least in theory!
This code was added for transitioning from the old data format, now that
it is no longer in use, probably isn't needed any more. At some point
older version will stop working anyway as I'm not testing for full
backwards compatability. But I'll leave it in for a little while longer.
The problem is that if a beta had been released, then when the next
beta, or the final release was first added it would override the beta.
This would then set the status to unreleased. The whole release_status
mechanism is a bit messy and may need to be reconsidered.
So that the hah values remain the same as they are on master.
Probably more effort than was required to manually fix the hashes every
time they change, but I was getting a bit fed up of that. Although I
suspect some reason will still come up so that I'll have to manually fix
the hashes again.
Currently no way to update it (apart from manually, which is awkward),
but the plan is to do so automatically.
This messes up the hashes again. Probably best to resolve manually,
although it might be possible to emulate the old hashes.
- Both are now stored as strings.
- Unpublished articles have a null pub_date.
- last_modified is now always the last modified date,
before it was the pub_date once published.
