Skip to content
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

Release v3.1.0.0 #198

Closed
wants to merge 8 commits into from
Closed

Release v3.1.0.0 #198

wants to merge 8 commits into from

Conversation

IshaanDesai
Copy link
Member

Compatibility release for preCICE v3.1.0

BenjaminRodenberg and others added 8 commits February 12, 2024 17:49
Add notes on docker release and point to #195
Fix numbering
We assume that this user has already been created in the base image.
* Update release guide

* Update docs/ReleaseGuide.md

Co-authored-by: Benjamin Rodenberg <benjamin.rodenberg@cit.tum.de>

* Update docs/ReleaseGuide.md

Co-authored-by: Benjamin Rodenberg <benjamin.rodenberg@cit.tum.de>

* Update docs/ReleaseGuide.md

Co-authored-by: Benjamin Rodenberg <benjamin.rodenberg@cit.tum.de>

* Rewording pre-release

---------

Co-authored-by: Benjamin Rodenberg <benjamin.rodenberg@cit.tum.de>
@IshaanDesai
Copy link
Member Author

While releasing a preCICE bigfix (v3.1.1), the issue of doing an empty release of the bindings was brought up. After some discussions, it was concluded that bindings will not be released for preCICE bigfix releases. The versioning scheme of the bindings will also be changed. Henceforth the bindings versions will have three numbers: {preCICE major version}.{preCICE minor version}.{bindings patch}. These conclusions mean that this release is no longer necessary.

@IshaanDesai IshaanDesai deleted the python-bindings-v3.1.0.0 branch April 12, 2024 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants