in-progress release notes #1987
Description
pdimov is requesting that the website display "in-progress release notes". A logical place to show those would be on webpages similar to boost releases:
https://www.boost.org/releases/develop/
https://www.boost.org/releases/master/
In AWS S3, release-notes files exist here:
bucket_name/release-notes/master/boost_1_90_0.adoc
bucket_name/release-notes/develop/boost_1_90_0.adoc
on both staging and production.
"in-progress release notes" should probably calculate the future boost version based of the 'latest' version. Currently, 'latest' is 1.89.0, so in-progress is 1.90.0, and that's the file to detect.
Later, what if it searches for the file boost_1_91_0.adoc, and that's missing? Show a fallback default text message "Future in-progress release-notes will be displayed here". Or, nothing. Don't continue to show a previous version.
website-v2-docs is uploading those files in GHA. If website-v2 provided a webhook mechanism (merely a GET request to a URL in the admin panel), website-v2-docs could alert website-v2 that release-notes need to be processed. At the same time, also, add a once-per-day, infrequent, scheduled celery task to achieve the same thing, which directly calls the function. This is in case the webhook isn't yet working, or isn't being called.