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

OpenFOAM 6 support not included in release v2.0 #3

Closed
gcapes opened this issue Nov 15, 2018 · 3 comments
Closed

OpenFOAM 6 support not included in release v2.0 #3

gcapes opened this issue Nov 15, 2018 · 3 comments

Comments

@gcapes
Copy link

gcapes commented Nov 15, 2018

The installation instructions don't make it obvious that I need to clone the repo in order to get the of60/src directory.

@fppimenta
Copy link
Owner

fppimenta commented Nov 15, 2018

As explained in the changelog file or the changelog section in the user-guide, support for of60 only became available from rheoTool version 3.0. Therefore, tag v2.0 (version 2.0) is missing this support.

If you want to use the most updated version of rheoTool, you should clone or download the repository (it will automatically point to the latest commit). Releases are tags to older versions (they are created once a new version comes out) and shall not be used for such purpose. I know this can sound strange. For example, version 3.0, which is the current one, is still not tagged as a release (it will be once a new version is out), but can be obtained by cloning/downloading the repo.

@gcapes
Copy link
Author

gcapes commented Nov 16, 2018

It does sound strange to only 'release' a version once you've released the next one. I might not be the only person who thinks that they should download an official release in order to be using stable code. I'm just making suggestions on how to make the documentation more user friendly.

@fppimenta
Copy link
Owner

Yes, it is indeed not the 'usual way' to do it. We will add a note in the user-guide or readme clarifying the purpose of releases (tags to older versions). The newest commit in the master branch is the stable code.

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

No branches or pull requests

2 participants