RELEASE: v0.8.0

[choldgraf]

Description

Now that we've finished up the last issues that were blocking a release (specifically #535 is resolved), let's cut a release since we've made several improvements in the last few weeks!

Checklist

• Bump __version__ in __init__.py. Use semantic versioning to decide whether it's a major, minor, or patch bump.
• Make a release commit: git commit -m 'RLS: v0.2.0'
• Push the RLS commit git push upstream master
• Make a GitHub release
  • Call the release the current version, e.g. v0.2.0
  • In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
  • In the Target: dropdown, pin it to the release commit that you've just pushed.
  • Add release notes in the field below (if it's a minor/major version bump)
    If you wish, use github-activity to generate a changelog, eg github-activity pydata/pydata-sphinx-theme --since v0.2.2 --until v0.3.0.
  • Confirm that this github action job has completed successfully in the actions tab
  • Confirm that the PyPI version is updated
• Celebrate, you're done!

[damianavila]

Congrats on the release, @choldgraf!!

I know there was some pressure from a previous failed release to make this happen ASAP, so take my points lightly... just thinking about things for the next iteration:

• Let's create an RC before the next release
• Let's avoid issuing a release during the weekend 😉

[choldgraf]

@damianavila I agree with your suggestions - in this case, I wanted to make the release quickly because apparently ReadTheDocs did not get the memo the last time the release was rolled back. I viewed this as a follow up to the previous (aborted) release attempt.

Let's discuss the other two points in follow-up issues?