Whoosh...the sound deadlines make as they go passing by. :) Today was our target for 3.5RC1. A quick glance at JIRA, however, reveals we're still a bit of a way off. https://issues.jasig.org/browse/CAS/fixforversion/11788
The good news is we've already made a lot of progress on this release since last fall and lot of the code is already in production at a number of sites, this includes: * OAuth Support (thanks to our newest committer Jérôme Leleu) * Ehcache Ticket Registry * Improved TGT policy * Upgraded to Spring 3.1 and dependent libraries * New language support (Farsi, Arabic, traditional Chinese) * A host of other fixes and improvements The remaining issues seemed mostly centered on: * Monitoring & Management Framework * Improvements to Services Registry * Improvements to configurability * LPPE - Alternative login flow based on account status (locked, password expired, etc) * ClearPass * Licensing clean up * Other minor fixes and improvements. There's already a lot of work done in these areas as well, so I on the surface it doesn't look like we are too far off. I'm still hopeful that we can get to a GA release in time for Jasig/Sakai conference in June. Given that as the goal, how do folks feel about pushing the RC release out to say May 18th and making that a hard deadline, meaning scope will be cut if a particular issues is not ready by then? This would set us up for a GA release late May / early June. Thoughts? Bill -- 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-dev
