Release strategy: more prominence to cut-off dates (even if estimates subject to change)

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?