chore: tidy up meterials post rebrand - #151
Merged
Merged
Conversation
Signed-off-by: tison <wander4096@gmail.com>
Member
|
The CHANGELOG history file doesn't need to be renamed, because this is a continuation of the project. |
Member
Author
This is one possible choice. But I choose to archive old changelog, which is also a typically option. For example:
I always consider contributors can adopt the style they like, so would not spend time on bikeshedding this. |
Member
Author
|
That is, I'd prefer to archive old changelogs from time to time to keep the most interesting ones short enough to open and search. Typically, users migrate from recent versions, and keeping an arbitrarily long changelog doesn't help. I may do the same action for a 1.0 version to archive all pre-1.0 changelog. |
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
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.
No description provided.