> I would > assume that this project lines up with the roadmap for CAS 4.0 and would't > fit in CAS 3.5 or even CAS 3.6. Is that a reasonable assumption?
I pictured taking into account any impact the design might have on the authentication API changes slated for 4.0, but don't necessarily see the spec implemented for 4.0. I've yet to carefully review the proposal, but I assumed there would be some substantial API and moreover protocol changes that would cause undesirable scope creep for 4.0. I'm still in favor of a tight and short-cycle 4.0 release. > If so, what is the state of CAS 4 development? I've been holding off on a big merge for authentication API changes until after a 3.5.1 release. After that master will become the primary branch for 4.0 development. > Would we want to create a > fresh feature branch for LOA from the current master (which I'm assuming > corresponds to the current work on version 3.5)? Possibly, but in my mind it's too soon to say. I don't think we've come to consensus on a design much less implementation. Once we come to consensus here, I'd like to invite some broader review of the design outside the CAS community. I think there's a lot of potential here, and I'd like to get the design right such that it's simple yet extensible, and thereby follows a similar pattern that has served us well in the past. 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
