Automatically generate release boilerplate #1165
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
achow101
force-pushed
the
release-automatic-front-matter
branch
from
b4ea93d to
16607ad
Compare
|
Concept ACK |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release posts contain a lot of boilerplate that is copied from one release to the next with the only change being the version number. There is also boilerplate added around the release notes, and boilerplate in the blog post announcement post. Updating all of these manually is prone to error and requires manual checking. This PR automates all of these to simplify the release publishing process by using a custom jekyll plugin. This changes a release post to only need the date, release version, magnetlink, and release notes to be added. The rest will be generated automatically by the plugin. For the plugin to work properly, all of the translated releases are also moved from
_poststo_releases, but no links change.Additionally, the release blog post will also be generated automatically. The text of the post is contained in translated templates that are based on the release blog posts of the most recent releases. If a release blog post is added manually, this step is skipped. To verify that this is correct, the release posts of the most recent releases are deleted. To avoid having this apply retroactively, it is also limited to generating the release blog post for 28.0 and later.
Lastly, I noticed that links to alternate versions of a release post were incorrect. The first commit of this PR fixes these links.