-
-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Solver dummy extension (#48) * Rename fulfilledAction, fulfilled_action -> markActionFulfilled, mark_action_fulfilled. #29 * Changing API call isTimestepComplete to is TimeWindowComplete * Extends solverdummy to include data transfer * Changing non-PEP8 complaint variable names * Removing parallel solverdummy Co-authored-by: BenjaminRueth <[email protected]> Co-authored-by: ishaandesai <[email protected]> * Provide compiler_directive language_level to avoid warning. * Add CHANGELOG * Add release guide * Update CHANGELOG.md * Bump version to release for preCICE v2.1.1 Co-authored-by: Kyle Davis <[email protected]> Co-authored-by: BenjaminRueth <[email protected]>
- Loading branch information
1 parent
7307c87
commit 2d3018a
Showing
5 changed files
with
97 additions
and
5 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Changelog of Python language bindings for preCICE | ||
|
||
All notable changes to this project will be documented in this file. | ||
|
||
## 2.1.1.1 | ||
|
||
* Bindings can now handle mesh initialization with no vertices. This behavior is consistent with the C++ preCICE API. | ||
* Adds a CHANGELOG to the project. | ||
|
||
## 2.1.0.1 | ||
|
||
* Update solverdummy to include data transfer. | ||
|
||
## 2.0.2.1 | ||
|
||
* No relevant features or fixes. This version is released for compatibility reasons. | ||
|
||
## 2.0.1.1 | ||
|
||
* No relevant features or fixes. This version is released for compatibility reasons. | ||
|
||
## 2.0.0.2 | ||
|
||
* Improvement of PyPI intergration. | ||
|
||
## 2.0.0.1 | ||
|
||
* Introduces new versioning system. See https://github.com/precice/python-bindings/issues/31. | ||
* First independent release of the python bindings. | ||
* Name the package `pyprecice`. | ||
* Publish package on [PyPI](https://pypi.org/project/pyprecice/). |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
## Guide to release new version of python-bindings | ||
The developer who is releasing a new version of the python-bindings is expected to follow this work flow | ||
|
||
1. The release of the `python-bindings` repository is made directly from the latest commit of the `develop` branch (no independent release branch). | ||
|
||
2. Bump the version to the appropriately in [`setup.py`](https://github.com/precice/python-bindings/blob/develop/setup.py) (i.e. `precice_version = version.Version("2.1.1")` and `bindings_version = version.Version("1")`). *Note:* If a pre-release version is being made then the `rc` key in the `bindings_version` attached (i.e. `bindings_version = version.Version("1rc1")`). | ||
|
||
3. [Open a Pull Request from `develop` --> `master`](https://github.com/precice/python-bindings/compare/master...develop) named after the version (i.e. `Release v2.1.1.1`) and briefly describe the new features of the release in the PR description. | ||
|
||
4. [Draft a New Release](https://github.com/precice/python-bindings/releases/new) in the `Releases` section of the repository page in a web browser. The release tag needs to be the exact version number (i.e.`v2.1.1.1` or `v2.1.1.1rc1`, compare to [existing tags](https://github.com/precice/python-bindings/tags)). Use `@target:master`. Release title is also the version number (i.e. `v2.1.1.1` or `v2.1.1.1rc1`, compare to [existing releases](https://github.com/precice/python-bindings/tags)). | ||
*Note:* If it is a pre-release then the option *This is a pre-release* needs to be selected at the bottom of the page. Use `@target:develop` for a pre-release, since we will never merge a pre-release into master. | ||
|
||
a) If a pre-release is made: Directly hit the "Publish release" button in your Release Draft. Now you can check the artifacts (e.g. release on [PyPI](https://pypi.org/project/pyprecice/#history)) of the release. *Note:* As soon as a new tag is created github actions will take care of deploying the new version on PyPI using [this workflow](https://github.com/precice/python-bindings/actions?query=workflow%3A%22Upload+Python+Package%22). | ||
|
||
b) If this is a "real" release: As soon as one approving review is made, merge the release PR (`develop`) into `master`. | ||
|
||
6. Merge `master` into `develop` for synchronization of `develop`. | ||
|
||
7. If everything is in order up to this point then the new version can be released by hitting the "Publish release" button in your Release Draft. |
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
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
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