Since noone else seems to say a word. I personally didn't understand at all why v1.0.2 when its end-of-life is in sight already. Now you have to continue to track three active branches. But this is your problem of course.
What i _really_ don't understand is why 1.0.2 is delivered with false documentation (not only "int SSL_CONF_finish(SSL_CONF_CTX *cctx);") etc., especially given that there are bug reports. Documentation is a vivid part of a software, especially when a completely new interface is introduced. From only the documentation you won't be able to get that stuff going. Is ALPN, a prominent member of the NEWS entry (you find it on the website), at all documented? Where can i find a word about it?? So why that hastiness, now that OpenSSL gains enough money to pay the bread of not only one, but indeed multiple fulltime developers. And then the sponsors seem to accept spending time for tree re-evaluation? Is the OpenSSL project at the Wall Street and needs to produce hyper-hyper quarterly reports? That is really strange. Ciao, --steffen _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev