Add additional variables to the release note files to allow setting the
version number and date. The version number is required, and can be
used to automatically set the release notes title. The date is optional
and can be set hours/days after the release.
Additionally, a Makefile test is added that checks whether the download
files exist on the Bitcoin.org server. This can help prevent creating a
broken Download page.
* Set variables for all previous releases
* Document variables in README.md
* Update code and templates to use variables
* Add the Download page links to the "dl" CSS class. Also add newlines
to make the HTML a bit easier to parse using sed
* Add a new Liquid plugin to print warnings. This is used to print a
non-error warning if any release is created without the optional date
This commit adds an extra step to the build process to SHA256 checksum
all the files that are built purely based on repository contents. The
checksums file is uploaded to the webserver with the rest of the site
content.
A separate target is added to the Makefile to compare the remote
sha256sums file to a locally-built file to see if they differ. This
allows us to detect when a remote build may have gone astray.
Make releases notes layout and urls consistent with the alerts page
Add RSS feed in download and version-history pages
Add a canonical page with a redirect to the new url
Simplify releases notes layouts
Generate alerts pages through alerts.rb plugin
Allow to keep short alias urls for each alert
Move alert pages in _alerts
Update sitemap plugin to include alerts
