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 1.0.1 #2768
Comments
One potentially controversial statement in Challenge to scientists: does your ten-year-old code still run? Nature 2020 doi:10.1038/d41586-020-02462-7
provides some additional motivation for making sure that we have a stable Python 2.7-capable release. |
- Fixes #2768 - backport fixes from 2.0.0 development version to the 1.0.x branch (master) - includes backports of all fixes tagged with Milestone 1.0.x (currently 1.0.1) via cherry-picked commits
The fix for #2984 could be backported. |
So after some off-github discussions with @lilyminium and @richardjgowers, we were wondering how everyone would feel about pushing for a rapid 1.0.1 release where we disable nsgrid completely and then have aim for a 1.0.2 release with @richardjgowers' fix? If the mailing list is any indication, quite a lot of people are facing issues with things that are now fixed in pinging @MDAnalysis/coredevs here. |
+1 for releasing an interim 1.0.1 as strictly better than keeping 1.0.0 until the fix is in (e.g. all the pytest failures) |
And #2427! |
I'll backport PR #2427. |
Outstanding backports/fixes |
The deprecation of hbond.waterbridge analysis in PR #2913 could go in 1.0.1 if it gets turned around quickly. Otherwise we make a 1.0.2 soon-ish. |
Unfortunately, I broke Travis for master (see PR #3011) so that PR also has to go through before we can wrap 1.0.1. |
Just FYI unless there's any objections, I'm going to declare a code freeze on 1.0.1 (excluding release related CI/maintenance stuff). There's a lot of things that still need deprecating/backporting (e.g. #2913, #2857), and then the nsgrid fix, so we'll need to cut a 1.0.2 release for them. I still have hopes we can release this week, assuming we don't encounter more upstream issues... |
Release 1.0.1 has been completed -- closing |
A few things are accumulating for a patch-level release for 1.0, related to
The point is to make 1.0.x a stable platform for anyone who needs legacy MDAnalysis for the foreseeable feature. 1.0.x should not be worse than 0.20.1.
The text was updated successfully, but these errors were encountered: