...
Grouper releases are versioned according to the following versioning pattern Major.Minor.Patch. Implementers can expect compatibility within Minor releases, namely all 2.1.x versions will maintain the same API calls. Software compiled against 2.1.0 can be expected to link against 2.1.99 without requiring changes to custom code. Occasionally, you may have to recompile against a Patch release due to changes in interfaces, but the API and old calls will still function. Releases across Minor versions may require small changes to custom developed modules, but are not expected to severely cripple existing deployments. Major releases offer no guarantee of API compatibility with existing softwareBuild. The Grouper Development team strives to maintain permanent backward compatibility of the core API across all releases.
Security Fixes:
Current and the previous two Minor releases will receive active security patching by the core development team. As of August 2013 that means the 2.1.x, 2.0.x, and 1.6.x releases are maintained by the core development team. Releases outside of this window will be patched on a case-by-case basis depending on several factors including: ease of development/testing of a patch for the version, compatibility of a patch for a supported release being applied to an unsupported release, and community contributions of patches for a targeted unsupported version.
...