-
Notifications
You must be signed in to change notification settings - Fork 15
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
Prepare Release 1.4.0 #98
Comments
Due to the adopted versioning approach (semver.org) we have to increment the minor number because we have changes in the SQL interface. The patch number is incremented when doing some changes that do not affect the interfaces. The last PR before the release will change version to 1.4.0. |
Oh, yes, of course. |
|
All pending 1.4.0 PRs are merged. Freeze the code for testing. The 1.4.0 tag will be assigned after some testing. |
I think 1.4.0 is ok. If no objections, I'm going to set a tag and create a release artifact. |
Closed as completed. |
Dear Community,
I new release 1.4.0 is coming. I would propose to implement the following functionality to be included into the release:
PRs are proposed to be applied:
New functions are proposed for implementation:
The text was updated successfully, but these errors were encountered: