Context

Thus far we've been bumping minor versions "as if" they were major versions. However, this isn't necessary as there is nothing inherently "special" about a 1.0 release. We are also sort-of locked into an anti-pattern where we have no explicit criteria for when to "start treating major versions as breaking and follow a normal semver minor/patch process".

Proposal

So I propose that whenever we drop JQuery and upgrade to Bootstrap 5 via the latest pydata Sphinx theme, we do these things:

• Make the next release 1.0.0
• Add a note in our documentation that there's nothing special about 1.0, other than that the next time we release a significant breaking change it'll be 2.0 now and not 1.1.
• Start following a semver-like process where we bump major versions with this criteria: "We've changed something that we expect will break a significant number of people's documentation builds unless they change something."

Tasks

• Remove JQuery and update versions #668
• Bump to 1.0
• Make a release and document this practice
• Close this and Time for 1.0.0? #622