Add release notes to separate folder #718
Merged
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.
Copied release notes to new folder at repo root, and converted to Markdown.
QA: Viewed partially rendered markdown locally, GitHub flavored Markdown means a full check locally is not possible.
This commit applies to FFTK-3255
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness
Overview
This will make it easier to properly test further work on FFTK-3255, which is decoupling the release notes from the documentation. Follow up PR will remove the rst, and replace sidebar release note links to point to the GitHub repo. This will allow for any changes/updates post release to easily be updated.
-s, --signoff
).-S, --gpg-sign
).Comments
Merging immediately, to aid with testing next update