Release 2.0.0

[IAlibay]

The target release date for 2.0.0 is the 10th of May.

This means that we want a code freeze that comes into effect next Friday the 7th of May.**

Please see the following for a list of all current things that need to get done: https://github.com/MDAnalysis/mdanalysis/milestone/16

If there's anything that isn't on there, please do bring it up here and/or add it to the milestone directly.

** Note: I'm not convinced this is realistic - I would still like to advocate for the possibility of a release candidate release by the 10th so that we have some spare time to get things done.

[IAlibay]

Hi all,

Our original plan was to release MDAnalysis 2.0.0 on the 10th of May, however given that:

1. MDAnalysis 1.1.1 was only advertised a few days ago
2. There are still many items left on the milestone target
3. The large API changes being introduced
   the core developers have decided to take a different approach for this release.

Our new aim is to do a beta (or release candidate) release on the 10th of May, and then follow up with a full release at the end of the month (currently set at the 28th of May). The beta (or release candidate) will be made available on pypi so that folks can start testing out the new features (and so that it can be used in the upcoming MDAnalysis workshop).

The plan is as follows:

1. A "soft" code freeze will be put in place for end of day Saturday 8th of May Eastern coast (8 am BST). Any commits that fail to make it in by then won't be included in the rc1/beta release.
2. Sunday -> Monday:
   • Merge develop into master (lead: @richardjgowers )
   • Cut a release (2.0.0b1 or 2.0.0rc1) and upload to testpypi/pypi (lead: @IAlibay )
   • Release a blog post explaining the release, and most importantly what features/bug fixes didn't make it in (and when the final release will be expected) (lead: @IAlibay )
3. beta/rc1 release gets used as the basis for the workshop
4. Anything currently on the 2.0.0 milestone + bug fixes (no more API changes) are accepted to be merged for 2.0.0 until the 24th of May (final code freeze deadline)
5. We get everything ready for final release for the 28th of May, if there are any bugs from the workshop, we address them then and then we release