-
Notifications
You must be signed in to change notification settings - Fork 232
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
RMG v2.4.0 (?) Release Planning #1591
Comments
Another topic for discussion: Would we like to begin official support for Docker with this release? For people not in the Green Group who may not know about this, we have been considering Docker as a way to offer a host-independent method of installing RMG. This can be especially useful for installing on HPC clusters which may already have support for Docker images. Somewhat surprisingly, there were already a couple of RMG images on Docker Hub. For testing, I've created a semi-official one which can be pulled: https://hub.docker.com/r/mliu49/rmg. The main benefit would be offering a streamlined option for running RMG on a wider variety of systems, including non-ubuntu linux systems and windows, at the cost of adding another system which we would need to manage and support. What this would entail:
|
Docker sounds like a decent idea, (though I'm not volunteering my own time to support it. I think @skrsna has done some docker stuff) I think 2.4.0 is reasonable. Nice to have 3.0 be the Python 3 version. May sounds like a good target |
I think we should merge #1496 and ReactionMechanismGenerator/RMG-database#296 |
Is it worthwhile to get in commits necessary for the Arkane paper? Like @mjohnson541 's quantum hindered rotors, and my reorganizing the output of Arkane? |
I agree, let's try to get it in |
RMG-Py v2.4.0 Release Notes (draft)
RMG-database v2.4.0 Release Notes (draft)(note that the tags here are odd because this issue is in the RMG-Py repo; the final release notes will be in the RMG-database repo so they will be normal)
|
Please feel free to edit the draft release notes above. I would also appreciate it if everyone could help keep this up to date as we merge more PRs before the release. |
Release is done! |
With the RMG-cat merge completed, I think we should have a new release soon. Potential target release date could be end of May. Please feel free to provide your own thoughts.
First, regarding the release number, I'm leaning towards
2.4.0
. The RMG-cat merge is a major new feature, but it didn't introduce any backward compatibility issues, so I'm not sure if it would necessitate jumping to3.0.0
. Also, thinking ahead, it would be nice to transition to Python 3 and fix our variable naming inconsistencies for the3.0.0
release, which would definitely involve breaking changes. Of course, this is also open for discussion.Next, we need to identify any issues/PRs which we want to include in this release. Potential list:
Please use this issue thread to comment on the status of currently open PRs and whether or not they can/should be included in this release. RMG-database PRs can also be discussed here rather than creating a separate RMG-database issue.
The text was updated successfully, but these errors were encountered: