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
Resolve gmxapi versioning with respect to GROMACS releases and packaging #188
Comments
We can allow that 0.0.7 only works with GROMACS 2019 and make this issue pertain only to versions 0.0.8 and higher. |
gmxapi development is moving to the GROMACS repository. This repository will continue to house gmxapi packages through 0.0.7.x, which will be tied to GROMACS 2019. I am updating the development branch and planning to merge it finally to 'master'. The 'release-0.0.7' branch will be allowed to lag behind master for stability, but merges will be staged directly against 'master' from now on. |
gmxapi 0.0.8 and GROMACS 2020 probably won't be compatible with 0.0.7 client code.
According to https://redmine.gromacs.org/issues/2764 GROMACS will probably change the reported compatibility in
gmxapi-config.cmake
from SameMajorVersion to ExactVersion, making it the client's responsibility to determine compatibility.kassonlab/gmxapi and kassonlab/sample_restraint can be updated to check for explicit gmxapi versions in reverse chronological order until we have a clearer compatibility guarantee. We can issue "tweak" releases on the release-0.0.7 branch to handle necessary compatibility tweaks.
Update: All gmxapi software for API levels > 0.0.7 is officially maintained in the main GROMACS repository. The current repository (as well as kassonlab/gromacs-gmxapi and gmxapi/gmxapi) will undergo some rearrangement to tie 0.0.7 software to GROMACS 2019 while keeping these GitHub repositories pointing to something useful.
devel
branch to master.release-0_0_7
.master
branch with the Kasson Lab GROMACS fork (thesandbox-gmxapi
branch from GROMACS Gerrit repository).The text was updated successfully, but these errors were encountered: