Bump to 0.5.0 and add optiSLang release note #408
Merged
Conversation
This file contains hidden or 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
dnwillia-work
approved these changes
May 12, 2022
| - Ability to use Fluent TUI commands for both meshing and solver features | ||
| - Ability to use Fluent's in-built post processing capabilities | ||
|
|
||
| This version of PyFluent is supported for Ansys optiSLang 2022 R2 release. |
There was a problem hiding this comment.
@mkundu1 I will add optiSLang folks here.
@tejalprabhu01 please review the above statement.
tejalprabhu01
approved these changes
May 12, 2022
seanpearsonuk
approved these changes
May 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the pyansys branching model,
release/0.5is the release branch for optiSLang consumption. After this PR is merged, I'll push a tagv0.5.0to therelease/0.5branch. Any new bug-fixes required for optiSLang will be merged to therelease/0.5branch and the branch will be re-tagged asv0.5.1and so on.The
mainbranch will be continuously updated with all planned changes including the optiSLang bug-fixes. The next dev release version for themainbranch will bev0.6.dev0.