Update changelog for the upcoming 0.6.0 release - #31
Merged
Conversation
Contributor
|
Can you add a paragraph in the README (under "Development") how to do releases now? |
Contributor
Author
Sure thing. In another merge request, if that's okay? |
Contributor
Author
|
I added that note in #33. |
coordt
approved these changes
Apr 27, 2022
Contributor
Author
diazona
force-pushed
the
update-changes-for-0.6.0/1/dev
branch
from
May 5, 2022 07:03
569a8db to
230f4a4
Compare
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
3 participants
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.
Everything listed under the 0.6.0 release milestone has been done (except this PR itself), so I figure it's time to release a new version. As usual, the April 27 date is just a placeholder; we should substitute in whatever we want to be the actual release date before merging this.
Anything else that should be added?