Sat 19 Jul 2025 9:09AM
Release strategy: more prominence to cut-off dates (even if estimates subject to change)
Nicola Tuveri
Public
Seen by 23
Having a discussion this morning at IETF, one thing that emerged is that contributors from our communities do appreciate the clarity given by the current version of https://openssl-library.org/roadmap/index.html but what still seems to be missing is an easy way to discover the planned cutoff dates associated with future releases: most prominantly, when is the feature freeze for future release 3.Y or 4.Z planned?
Is this something that the Academics community would like me to push for within BAC?
Tim Hudson Tue 29 Jul 2025 8:48AM
We know what those nominal dates are - it is just a matter of adding them to the page. There is a built in "buffer" allowing to unplanned events but we know the target dates already - and we know the total range of the "buffer". That is easy to do.
Nicola Tuveri · Sat 19 Jul 2025 9:10AM
@Billy Brumley I think this discussion is likely going to be of interest for you as well in the Corporation BAC.