There also appears to be committer consensus on the release strategy defined in the latest roadmap. The release strategy describes a PATCH release as:
PATCH - a conservative incremental improvement that includes bug fixes, enhancements and new features and is absolutely backward compatible with previous PATCH releases of the same MINOR release. (i.e. 2.4.15 is a drop in replacement for 2.4.14, 2.4.13, 2.4.12, etc.). Adopters can expect that major APIs, integration points, default behavior, and general configuration is mostly the same. CAS maven overlays should build with little to no changes, unless required and highlighted in the release notes. I would encourage everyone to review and comment on the roadmap and the release strategy: https://wiki.jasig.org/display/CAS/CAS+Roadmap Best, Bill On Fri, Sep 30, 2011 at 9:11 AM, Marvin Addison <[email protected]> wrote: >> I didn't even look, but is there a Migration Document available? > > No, but there should be. > >> I think these kinds of breaking changes ought to be documented. > > Totally agree. Ideally we will produce version-specific upgrade > documentation, but that is a lofty goal for a handful of documentation > producers. I think what is feasible in the near term is some brief > notes on changes that could break on upgrade with links to the commits > so that the interested reader could at least investigate and determine > for themselves what needs to be done. We will do our best to do this > going forward starting with 3.4.11. > > M > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
