Seems to be strong consensus for switching the repo “version” to “calendar versioning”, where releases are of the form 2022.09.14 instead of 2.0.0. The file names would remain unchanged (Sage = openff-2.0.0, Rosemary = openff-3.0.0, etc), but the git tags, python module, and conda packages would reflect the “calendar version” instead of the “force field version”.
How to version “ports” of external FFs/FFs whose reference implementations are defined elsewhere?
Would we want to add different ion models as well? Would we bundle them with compatible water parameters? How would we define compatible?
✅ Action items
⤴ Decisions
No labels
0 Comments
You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
0 Comments