With reference to the discussion #569 (comment) about wanting to release v2.4.0 before starting with a v3.0:

Any objections to creating a feature-v3.0 branch / development / next (name can be discussed) from master? This way the "v3.0" work can start now and not be obstructed by the finalizing of a v2.4.0 release. It's a temporary branch. Once v2.4.0 is out, we merge the feature-v3.0 branch into main and close it. I can take responsibility to keep this branch in sync with master and ensure that the commits we add to v2.4.0 are applied to the feature-v3.0 branch.