Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

2013-04-22 CAS4 Release Planning Call

Meeting Details

Tuesday, April 22, 2013.  14:00 - 15:00 US - Eastern (GMT -04:00)

Participants

Agenda

  • CAS4 objectives and scope
  • Review open Jira issues
  • CAS3 Protocol Revision
  • Release process/voting
  • Release engineer
  • Early Adopters

Meeting Notes

Release Process/Voting

Briefly discussed release process and proposal for more formally adopting Apache style release voting.  RC signals no new features. Encourage community to test. RC1,2,3 to address bugs or issues.  No new features. GA signals ready for adoption. Starts new dev cycle.  Marvin felt adopting release voting needed more discussion on cas-dev.

Release engineer

Misagh will be release engineering for this release, will work with Marvin to cut RC1.

CAS3 Protocol Revision

Bill will move current draft to protocol module in CAS repo.  Convert format to plain text or markdown.  Add Robert as a committer for cas protocol rev.

CAS4 Objectives and Scope

CAS4 AuthN API

Marvin would like to see CAS4 authN api changes and ldapative get into the release, wants to bump to get those in.  This is just api support for MFA.  No idea what the user interaction should be yet.

Misagh and Marvin will look for ways to work together on ldapaptive.

Consensus for a 6 weeks extension with a 3 week status call.   At that point we will make a call on cutting scope if it doesn't look like we'll be ready for the release.

Marvin will update roadmap, user/dev l ist.

Front-channel SLO

Jerome to take forward in collab in Marvin.  Still targeting CAS4.

OAuth Server side

Jerome to take forward.  Still targeting CAS4.

Early Adopters

Marvin/VT will deploy CAS4 into dev version for integration testing.  Expect to deploy shortly after release.

Jerome has a lot of customizations in CAS.  Running CAS3.3.  Looking to adopt new features of CAS4.  Will go to CAS4 at the end of year.

Unicon is working Evergreen State College on MFA project.  Target is production deployment by end of Summer.  May need to overlay some CAS4 AuthN API on CAS3.

Post Meeting Notes (catch-all, Alibi's)

  • No labels