Commit graph

6 commits

Author SHA1 Message Date
David A. Harding
cbebe461ff Releases: Variablize Release Notes
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
2015-02-27 08:15:50 -05:00
Saivann
2a139a51a1 Set license files and headers for bitcoin.org's content 2014-11-21 19:09:12 -05:00
Saivann
1ffd2cf573 Replace unused release announcement field by releases notes content 2014-04-12 17:21:24 -04:00
Saivann
fde77a23d0 Rename "Bitcoin-Qt" to "Bitcoin Core" 2014-03-19 15:43:55 -04:00
Saivann
3da682b36b Normalize page redirections
Use a fallback HTML page with a manual and javascript redirect
Keep canonical pages only for alerts
2013-10-14 14:59:10 -04:00
Saivann
6ac93df9f2 Generate releases notes using releases.rb
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
2013-06-19 14:04:29 -04:00