Work around JuliaLang/julia#34121 and Release 0.7.1 - #161
Merged
Conversation
Collaborator
Author
|
BTW, it might be a good idea to protect the |
Member
|
Looks like |
Collaborator
Author
|
I haven't yet rewrote the version number because in FixedPointNumbers.jl, it is a custom to rewrite the version number just before release, not just after release. However, we may want to use v0.8.0 (or v0.8.0-alpha or v0.7.1) now to clarify the order. (v0.8.0-dev is not good.) |
Member
|
In general, I only use release branches if I want to make further releases in an older release cycle. Otherwise I just release from |
Collaborator
Author
|
We already have some commits with breaking changes(e.g. 9155463), i.e. v0.7 is already in an old release cycle. |
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.
This backports PR #160.