Skip to content

Release 1.1.0#885

Closed
dwhswenson wants to merge 6 commits into
openpathsampling:stablefrom
dwhswenson:release-1.1.0
Closed

Release 1.1.0#885
dwhswenson wants to merge 6 commits into
openpathsampling:stablefrom
dwhswenson:release-1.1.0

Conversation

@dwhswenson

Copy link
Copy Markdown
Member

The marquee feature in OPS 1.1 is the addition of GROMACS support. That also introduces the external engine framework, which can be used by other MD engines.

Another important change is that OPS is now pip-installable and can be installed through conda's conda-forge channel (starting with 1.1, new versions of OPS will not be in the omnia channel). Also note that many tools that previously were bundled with OPS now are not. In particular, if you want to use any of the following packages, you must install them separately:

  • OpenMM
  • OpenMMTools
  • PyEMMA
  • MSMBuilder
  • Jupyter

They're all just a conda install away, and as soon as they're in your environment, OPS will interface with them as before.

Deprecations: CVs based on MSMBuilder featurizers are deprecated. MSMBuilder can no longer be tested in our standard test setup. We haven't removed support, but we can't recommend using it.

New features

Bugs fixed

Miscellaneous improvements

@dwhswenson

Copy link
Copy Markdown
Member Author

Now let's see if Autorelease is working -- mainly, if I correctly encrypted my passwords!

Note to those reading this (since a bunch of you just notified on the @-mention). The top post will be the release notes for OPS 1.1. They're written under the assumption you're reading them in a couple days. OPS isn't on PyPI or conda-forge yet, but will be soon! (I hope...)

I'll put out a tweet on the @pathsampling account once the conda-forge release is done (which will be the last step).

@dwhswenson

Copy link
Copy Markdown
Member Author

Aha... secure env variables aren't allowed in pull requests from forks. https://docs.travis-ci.com/user/pull-requests/#pull-requests-and-security-restrictions

Makes sense; I'd rather that a random person not be able to just make a PR that adds the line echo $TWINE_PASSWORD to our .travis.yml and then delete all my PyPI packages.

Secure env vars are allowed in PRs that don't come from a fork. All the projects I've used Autorelease with so far are in the dwhswenson GitHub account. I think the solution is to close this PR, push the commits to a branch openpathsampling/release-1.1.0 (instead of dwhswenson/release-1.1.0), and open a PR from that branch.

@dwhswenson dwhswenson closed this Dec 12, 2019
@dwhswenson dwhswenson deleted the release-1.1.0 branch January 21, 2020 13:55
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

Successfully merging this pull request may close these issues.

1 participant