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

release 0.20.0 #2240

Open
orbeckst opened this issue Apr 8, 2019 · 2 comments

Comments

@orbeckst
Copy link
Member

commented Apr 8, 2019

Catch-all issue for discussion of the 0.20.0 release. – please edit.

  • tag release-0.20.0 on master
  • release on GitHub
  • pypi
  • conda
  • docs
  • blog post
  • announce on
    • mailing lists
    • twitter

@orbeckst orbeckst added the release label Apr 8, 2019

@orbeckst orbeckst added this to the 0.20.0 milestone Apr 8, 2019

@orbeckst

This comment has been minimized.

Copy link
Member Author

commented Apr 8, 2019

There are plenty of issues tagged with 0.20 but I think these have to be migrated to either 0.20.x or 1.0. We have so much stuff in CHANGELOG, we really need to put out a new release.

We should also think about automating releasing so that we can just do a fixed schedule, say every 3 months we put out whatever we have (either a patch level or minor).

@orbeckst

This comment has been minimized.

Copy link
Member Author

commented Aug 7, 2019

@richardjgowers what do we have to do to make this happen?

In the light of dropping Python 2 #2303 I am a bit anxious to get one or two releases out before the year is over. In particular, we could do 0.20.0 right now, then drop 1.0 before the end of 2019 (last one with Python 2.7) and then soon after go to 2.0, which drops Python 2.7.

EDIT: see also https://groups.google.com/d/msg/mdnalysis-devel/UIPEFxwh_7o/qFlV5FVOAAAJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.