[META] Roadmap for 3.x

@ptmkenny Thanks for proposing this. I agree that it is appropriate to create a new branch. I'd like users to be able to update Sodium and Drupal core separately, which means having some overlap in dependencies between versions. I think that's the case with what you're proposing, but please confirm.

More specifically, I want to be mindful of the concerns and considerations Jakob Perry lists in this article:
https://medium.com/jakob-on-drupal/dont-go-making-major-version-changes-...

Yes, there will be overlap in support between the two versions (specifically both will support Drupal 10).

Sodium 2.x for Drupal 8 / 9 / 10.

Sodium 3.x for Drupal 10.3+.

The new major version has to be created because we need to drop support for PHP 7 because of 🐛 Cannot upgrade to paragonie/sodium_compat v2 because of PHP 7.2 Active . But we want to keep 8 / 9 on security coverage for as long as possible, so we will keep 2.x open and use 3.x to update halite.

This way, 2.x can be left open indefinitely with security coverage, while 3.x can use all the latest stuff from Drupal 11.

The issue to finalize this is here: 📌 Finalize requirements for 3.x and update README Active

This will set the requirements for 3.x as:

* PHP 8.1 (min for Drupal 10)
* Encrypt 3.2 (min for attributes support)
* Drupal 10.3+ (10.2 is the absolute minimum for PHP attributes support, but since 10.2 security support ends in December, and 10.3 includes all the features for D11 and the final version of the SDC module, I think it makes more sense to go ahead and bump the minimum to 10.3)

Great, thanks. The remaining issue to finalize looks good, so we're all set to go forward with the new version.

Thanks for the review!

3.0.0 has been released!

Automatically closed - issue fixed for 2 weeks with no activity.