Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: OpenSSL Release Strategy |
|
| Author |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
 Posted: Tue 06 Feb '18 20:18 Post subject: OpenSSL Release Strategy |
 |
|
As of release 1.0.0 the OpenSSL versioning scheme was improved to better meet developers' and vendors' expectations.
Later releases, such as 1.0.2a, exclusively contain bug and security fixes and no new features.
Minor releases that change the last digit, e.g. 1.1.0 vs. 1.1.1, can and are likely to contain new features, but in a way that does not break binary compatibility.
This means that an application compiled and dynamically linked with 1.1.0 does not need to be recompiled when the shared library is updated to 1.1.1.
It should be noted that some features are transparent to the application such as the maximum negotiated TLS version and cipher suites, performance improvements and so on. There is no need to recompile applications to benefit from these features.
Read More... https://www.openssl.org/policies/releasestrat.html |
|
| Back to top |
|
Jan-E
Joined: 09 Mar 2012
Posts: 1265
Location: Amsterdam, NL, EU
|
| Posted: Wed 30 May '18 7:52 Post subject: |
|
|
There is a new blogpost on the OpenSSL release policy:
https://www.openssl.org/blog/blog/2018/05/18/new-lts/
TL;DR is that the upcoming 1.1.1 will be the next LTS release. And that 1.1.0 will be supported 1 year after the release of 1.1.1. |
|
| Back to top |
|
|
|
|
|
|
