You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We released the last major release community.crypto 2.0.0 on 2021-11-01, which is almost three years ago. Since then we kept releasing 1.x.y bugfix releases.
I think it's time to stop releasing 1.x.y and declare 1.x.y End of Life.
The main breaking change of community.crypto 2.0.0, and the main reason for users to keep using 1.x.y, were:
Removal of the PyOpenSSL backends for almost all modules (openssl_pkcs12 being the only exception).
Removal of the assertonly provider in the x509_certificate provider.
Every other breaking change should be treatable with a bit of work, but these two probably caused the most pain.
I'd like to spread this issue for some time (at least a month) so that if everyone who still needs 1.x.y releases can comment here. If nobody needs them, we can stop spending any thoughts on them. (My guess is that nobody really needs them anymore, but since we don't have telemetry, 🤷)
Any opinions?
ISSUE TYPE
Feature Idea
COMPONENT NAME
stable-1 branch
The text was updated successfully, but these errors were encountered:
SUMMARY
We released the last major release community.crypto 2.0.0 on 2021-11-01, which is almost three years ago. Since then we kept releasing 1.x.y bugfix releases.
I think it's time to stop releasing 1.x.y and declare 1.x.y End of Life.
The main breaking change of community.crypto 2.0.0, and the main reason for users to keep using 1.x.y, were:
openssl_pkcs12
being the only exception).assertonly
provider in thex509_certificate
provider.Every other breaking change should be treatable with a bit of work, but these two probably caused the most pain.
I'd like to spread this issue for some time (at least a month) so that if everyone who still needs 1.x.y releases can comment here. If nobody needs them, we can stop spending any thoughts on them. (My guess is that nobody really needs them anymore, but since we don't have telemetry, 🤷)
Any opinions?
ISSUE TYPE
COMPONENT NAME
stable-1 branch
The text was updated successfully, but these errors were encountered: