3 ms·
The spec encourages the following, if a bad bug is found (cough openssl): 1.1 -> 2.2 -> 3.3 -> 1.4 -> 2.5 -> 3.6 And in fact I kind of like this. 1.4 is rathe
by falcolas 11y ago
The spec encourages the following, if a bad bug is found (cough openssl):
1.1 -> 2.2 -> 3.3 -> 1.4 -> 2.5 -> 3.6
And in fact I kind of like this. 1.4 is rather obviously compatible with 1.1 (and 2.5 with 2.2), but also clearly denotes a new release. You're still always using the most recent release, within a compatibility number.
Even better, it avoids crap like: "Affected users should upgrade to OpenSSL 1.0.1g. 1.0.2 will be fixed in 1.0.2-beta2." Instead, the fix is announced simply "Bug fixed in release 4 and later".
- bsimpson 11y agoI thought it said explicitly not to do that in the same paragraph: The Release Number SHALL NOT be decremented. Which would break exactly this us case if you followed to a T.