Conversation
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.
I've made a bunch of changes recently. I would like to do the following:
Publish v0.3.1, the current state of master, which contains near-field ptycho, a bunch of bugfixes, quality of life improvements, etc. as compared to v0.3.0, the latest version which is available on pip.
Then, I would like to start pulling in a bunch of changes, targeting v0.4.0, which will target:
Given the fact that the developer base is shrinking, I will probably start to do more self-code-reviews again, to avoid unnecessary delays, but I will still leave a few days between proposed changes and pulling into master, for the benefit of anyone working with the latest branch or who would like to be involved in discussions on specific features.