-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the next version #534
Comments
What would be wrong with |
(I have no objection |
oh right - I suppose so |
Yes, it would be 2.10. I'm generally happy to tag a release once someone provides feedback on the latest nightly to say it's all working ok |
This it can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@mattwire I was looking at the fact there are quite a few unreleased commits here & that they (among other things) make tests pass - but then when I thought about what version would need to be tagged I realised it either needs to be 3.0 - which implies a major version change - or a new naming convention - ie. 2.9.1
I have a feeling the handling for switching might not always see 2.9.1 as 'higher' than 2.9 - but that is just a vague 'haven't I seen this before niggle'
I probably would go to
3.0.0
with the 'major change' being that the versioning system has changedThe text was updated successfully, but these errors were encountered: