-
Notifications
You must be signed in to change notification settings - Fork 190
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
A new release #184
Comments
The version number certainly depends on if we care about orphan instances. It is a bug fix release if we don't care, it is possibly higher if we do (2.7.0.0). It might be helpful to document the versioning scheme in the wiki for this purpose. |
Agreed, a performance regression is not acceptable. Might as well merge #186 then. |
#205 has been merged. |
@eborden I vote for 2.6.3.0 as a new version. |
I'm now trying to update CHANGELOG. Please wait for a day or so. |
@kazu-yamamoto Agreed on 2.6.3.0 as we are deferring the |
@eborden OK. I have updated CHANGELOG. Please check. If you are fine with it, please make a new release:
I will go on a summer vacation from tomorrow to Tuesday. So, I will be inactive for a while. |
Thank you all for your contributions! |
Thanks very much! |
@eborden Let's collect working items:
First, let's decide how will work for each item.
The text was updated successfully, but these errors were encountered: