5.0.0 release planning (released 2022-04-07)

[willkg]

This covers figuring out the plan for a 5.0.0 release.

I'd like to get a 5.0.0 release soon because I have a window of time I can work on it. Ultimately, I want to reduce the maintenance burden, so I'd like to focus on reducing complexity, reducing docs, reducing code, reducing scope of the project, and simplifying workflow.

I figure we can call it 5.0.0 for now. Since we're dropping support for Python 3.6, I tend to treat those as backwards-incompatible events.

Let's use this thread to work out the details of the release and who is planning to do what.

[willkg]

Greg suggested these goals for 5.0.0:

• fix CI
• rework how we manage dev dependencies to make it easier to manage dev environments and CI environments (move requirements in requirements-dev.in to setup.py #620 )
• establish our target browsers and drop support for legacy browsers (update goals / non-goals #627 )
• figure out the plan for sanitizing CSS (rework how bleach.clean sanitizes css #633 )
• drop python 3.6 support (Drop support for EOL Python 3.6 #629 )

I also want to triage and cleanup issues and PRs and fix/land whatever is shovel-ready and/or easy to decide on and do.

[willkg]

We've covered just about everything I threw in the 5.0.0 milestone. The only thing left is looking at where we're at with type annotations.

I think I'm out of time/energy for 5.0.0, though, so while I think type annotations are really helpful and would help here, I'm going to bump that to a future release.

[willkg]

I pushed out 5.0.0 just now.

Unless we need to do a bug-fix release, the next release for Bleach will be when Python 3.11 releases.