My take on the upgrade is that it's pretty disruptive. The 1.3.0 release is a pretty big change from 1.2.1, and we're going to have to provide some new code to be feature compatible. Minor things like the exception translation changes are easily accommodated, but the new concept of AuthenticationStrategy means we have to write (albeit small amount) of custom code to get DIGEST-MD5 to work. Support for TLS will likely be a _lot_ better, so there may be significant benefits for CAS deployers with 1.3.0, but new code means more testing than a few hours on a Friday.
M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev