Release 2.2.0

[IAlibay]

As discussed elsewhere, our intention is to have a relatively quick turnover for the 2.2.0 release of MDAnalysis. The plan is to complete a few long standing items that unfortunately couldn't make it into 2.1.0 and ship it as soon as that happens.

As such release 2.2.0 should be shipped as soon (within a minimum of 1 month from today) as the following three PRs are merged:

• An "accurate and reliable" RDKitConverter #3044
• On loading the same XTC offset in parallel #3375
• increased the maximum number of matches from an rdkit smarts query #3470

[IAlibay]

🎉 🎉 🎉

We've reached all our requirements for the 2.2.0 release.

@MDAnalysis/coredevs we are in a complete code freeze except release related things / hotfixes please.

I'll start working through the TODO list this evening.

TODO

• Finalize changelog and update versions to 2.2.0 (merge to develop) finalize release 2.2.0 #3690
• Create release-2.2.0 tag
• Create package-2.2.0 branch
• Add rebuilt C files to package-2.2.0 branch
• Create package-2.2.0 tag
• Wait for action to build src and wheels for testpypi and then test them
  • Fix macos runners and wait until they go green
• Get @mikemhenry to test the release on his MacMini
  -17412 passed, 357 skipped, 2 xfailed, 2 xpassed, 7710 warnings in 107.76s (0:01:47)
• Publish the release
• Start 2.3.0 - unfreeze develop
• Update conda-forge feedstock
• Create a blog post for the 2.2.0 release blog post to announce 2.2.0 MDAnalysis.github.io#231
• Tweet out the release
• Finally create a blog post outlining our NEP29 strategy (given we've finally more or less caught up, but we'll be doing probably ~ 6 months behind in practice).

[orbeckst]

@IAlibay you know, you could close the 2.2.0 milestone if you wrote a quick NEP29 blog post ;-).

[orbeckst]

I opened MDAnalysis/MDAnalysis.github.io#238 for the NEP29 blog post and close this issue because as far as users go, we very much have a 2.2.0.