Release Report enhancements

[sdarwin]

Here are some proposed ideas to consider for release reports:

1. Add beta reports (for internal use only). This is a chance to test the full procedure each time a beta is published. Since current reports are probably based on an official boost release, there may need to be code changes to allow a beta report. If the process can auto-detect the latest version, either an official release or beta, it would not require any new --flags.

2. When a release report is generated, upload it to the S3 media folder and host it with a boost.io or boost.org URL, rather than an AWS S3 URL.

3. (Possibly, to think about...) when "Do It All" runs the last step of that could be to generate a release report and upload it, if that is not happening already. Therefore, clicking a Release Report button in the admin panel would not be necessary, although it could be optional to regenerate the report again. The data import (Do it All) and the report generation would be linked, and occur at the same time. In the admin panel, allow pre-configuring descriptions and information, so that when a Report is generated later on, it picks up that information.

[rbbeeston]

Hi @sdarwin - a few notes:

1. I'm in favor of this, and additionally it may be useful for setting up for the actual release. for example, the cartoon image, when added to the beta could automatically be added to the release when it happens. Same with the FSC statement.

2. that has always been part of the plan, what has made it difficult is the actual backend generation of the PDF file. @GregKaleka can probably speak more to this.

3. Yes, that should be happening, however, we would need a way to determine if it's for an actual release or a draft, we don't need to be moving drafts to the S3, at least without a convenient way of removing them.

[sdarwin]

at least without a convenient way of removing them.

Yes! They should go to another folder such as "drafts". And there should be a way to delete them.