The following makes up the project's current policy on providing feature updates, security patches, and informal support through the mailing list for current and older software versions of our components. Over time this policy may evolve, and we will announce such changes.
Strict versioning policy mostly ensures deployers can use minor-level upgrades without negative functional impact, so there is rarely a separately designated previous stable release.
We also provide specific guidance on the versioning of Java and C++ components and products and the impact on compatibility.
...