Planning post-BIP340 release

[conradoplg]

I think there might not be a way to add the taproot PR without a major version bump 😢 (which is a bummer because we just released 2.0.0)

The main issue is the addition of a Context associated type, which requires all ciphersuites to specify it. This could be introduced without a major bump if it had a default value, but that feature is not stabilized yet.

I thought about only adding the associated type if a certain new feature is enabled (e.g. ciphersuite-context). But that is a pain due to feature unification, for example on our own ciphersuites there would be no way to to tell if that feature is enabled in frost-core or not in order to know if the associated type must be specified or not.

Options I see:

• Get rid of the associated type. It's possible, the original PR before my cleanup didn't have it, but it makes everything else more painful (i.e. instead of just passing the Context around, it would require passing all the possible information that might be required to rederive that Context).
• Just merge it and release 3.0.0-rc.0 next.
• Merge it into a release-3 branch or something similar, and make a 3.0.0-rc.0 release out of it. We wait a bit while we gather other possibly breaking changes to include in the final 3.0.0. If we need to release e.g. 2.1.0, we can release that from main.

Any thoughts?

[conradoplg]

This is now moot because we didn't require Context 🎉