Things to discuss
(probably not all of these make it onto this meeting's agenda)
- UATs become automated functional tests that run nightly. Concretely, who's going to do what when and where?
- Jason Shao idea wrt uPortal CAS security provider and Java CAS client bundling with uP core. Move CAS security provider source code into uP core source tree?
- CAS 3.0.1 status
- CAS 3.0.2: goals
- Resource availability: it's pretty clear we're all busier than heck. Realistically, what resources do we expect when?
- CAS and Sakai. csev's idea of bundling CAS into Sakai.
- CAS and uPortal. Luminis model of including a CAS server in the uPortal bundle.
Agenda
uP 3.0.1 final release post action report
Quick review of what's in 3.0.1. Thanks to Scott for release engineering work, Drew for UAT heroics. Moment of basking in feeling good about having made a release.
Engineering the release process
Resources
- Yale: Drew and Andrew: finish producing automated functional tests for all UATs persuant to less heroics for release. Timeframe: After immediate Sakai heroics but before 3.0.2. Expected delivery in 3-5 weeks.
- Yale: Drew and Andrew: automate nightly build process to actually run all these functional tests against a CAS instance deployed into an SSL'ed Tomcat. Timeframe: After immediate Sakai heroics but before 3.0.2. Expected delivery in 3-5 weeks.
- Yale: Howard: Yale Shib pilot project, fronted and consumed by CAS. Immediate term (over the next month). Will have deliverables suitable for inclusion in CAS 3.0.x (fully backwards compatible) and 3.1.x (incremental evolution).
Futures
3.0.2
- Reaffirmation of policy on urgent issues: critical bugs, security issues for which a known fix: get them fixed and out in an ASAP release.
- Barring such a catastrophe, reasonable estimation of 3.0.2 timeline and content
- Realities of academic term starting: realistically, no release sooner than Sept 15th or so, right?