Prepare release of v2.3

[rtpg]

I looked over all the changes since the last tag and the changelog seemed correct, so I'm just optimistically placing the date in the changelog to today.

[codecov[bot]]

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@eb37046). Click here to learn what that means. The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #196   +/-   ##
=========================================
  Coverage          ?   92.97%           
=========================================
  Files             ?       11           
  Lines             ?      527           
  Branches          ?       66           
=========================================
  Hits              ?      490           
  Misses            ?       23           
  Partials          ?       14           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update eb37046...029e6aa. Read the comment docs.

[rtpg]

@timgraham so previously in #150 you prepped a release. I think here you could generate a new release by merging this, tagging it 2.3, and doing whatever you ended up doing last time.

I'm not 100% sure of the "right" process here, though. If you don't have time to handle this at the moment please say something and I'll try to bug some other people who I think might be able to move this forward

[timgraham]

The release process has changed since I last did it. I merged this and pushed the tag but it looks like one of the leads (@felixxm @hramezani @claudep) need to approve the packages to be uploaded from Jazzband to PyPI.

[felixxm]

@timgraham Thanks :rocket: Approved :heavy_check_mark: