Dropping v3 compatibility plans in README.md #2713
Merged
Conversation
This file contains 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
|
Oops, meant to approve instead of merge this. Anyway I don't think it matters much. |
|
Sure. What matters to me then is if you'd like to release v4.1.0 now or you plan to do something with midzoom code (like merge it as a whole or maybe just some pieces)? |
|
Let's release 4.1.0 now (could you do that?). And immediately afterwards I will merge midzoom, so we have a couple of weeks to accept any PRs on the midzoom code before rolling it out to osm's servers. I think it's best to merge big changes early in the release cycle. |
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.
Related to #2666.
I think we're ready to drop v3 compatibility plans now and go on with v4.1.0 release soon. If that's the case, project documentation should reflect it.