docs: drop the per-release notes pages - #10
Merged
Conversation
Four files, about 24K, restating what the changelog already records plus install instructions for a version nobody installs any more. They were kept as published and never updated, so they aged into a second, stale account of the project alongside the changelog. docs/ now describes the repository as it currently stands. Version history lives in CHANGELOG.md and on the releases page, which is where a reader looks for it. The README pointed at docs/release-notes-*.md; it points at the releases page instead. No other tracked file referenced them, and every remaining docs link resolves.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Four files, about 24K, restating what
CHANGELOG.mdalready records plusinstall instructions for a version nobody installs any more. They were kept as
published and never updated, so they aged into a second, stale account of the
project alongside the changelog.
docs/now describes the repository as it currently stands. Version historylives in
CHANGELOG.mdand on thereleases page.
The README pointed at
docs/release-notes-*.mdand now points at the releasespage. No other tracked file referenced them, and every remaining
docs/linkin the repository resolves.