Draft
Conversation
Member
Author
|
I forgot about #244! Should I just make this the 1.0 release? I'm inclined to! I'm pretty over the whole "everything is forever in 0.x.y" purgatory. We're still "breaking" releases every time we release a 0.x+1.y release, and it ties our hands from distinguishing bugfix (patch) from additive (non-breaking) releases. And it's no big deal if the next next breaking release would then be 2.0.0, and so on. |
Member
Author
|
Let's merge #273 first. |
michaelkirk
force-pushed
the
release/0.25.0
branch
from
ff2df90 to
70e6b17
Compare
Member
|
I'm in favour. |
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
2 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.
CHANGES.mdif knowledge of this change could be valuable to users.Draft because it depends on #273
I'm hoping to find a volunteer project or two to try out this version before releasing more widely.