On Wed, Jul 25, 2012 at 1:55 PM, jleleu <lel...@gmail.com> wrote: > Hi, > > I don't like big jump (3.5 -> 4.0), I prefer small steps (3.5 -> 3.6 -> > 3.7...) >
Me too. Biggest gain for the smallest change! :) >From a very high perspective, the CAS roadmap is pretty clear to me : > refactor the CAS core to handle more use cases and become compatible with > more protocols. > I'm not sure though that the problem is about defining which items should > be addressed in which versions, it's more about who can/want to work on > what item. Absolutely. I see things in a more opportunistic way : pull requests are somehow > "building" the roadmap and versions numbering. > Yes, versioning is derived from the Release Strategy. https://wiki.jasig.org/display/CAS/CAS+Roadmap There was consensus at the Jasig-Sakia conference around incorporating updated AuthN APIs that would require some Published Public API changes, hence planning around a 4.0 release. - http://www.jasig.org/cas/public-api That discussion is now underway here on cas-dev and the wiki to flush out planning for the next release. Hopefully we can more or less settle on scope in the August/September time-frame. > > That being said, I clearly lack a global vision to be relevant on the > roadmap. So I propose to tell you what I'm interested in and what I'm > willing to work on : > - OAuth : stable for 3.5.1 but still things to do in the future > - remember-me feature : in progress > - SLO > - LOA > - Block access to CAS services according to user attributes (maybe a bit > specific to be implemented in CAS) > - move services management webapp out of CAS server > - OpenId > - NoSQL as ticket storage (I know well MongoDB). > > Just let me know what fits best for next release. > Excellent! The way to determine what kind of release these would be suitable for is to review them against the Release Strategy. However, since it looks like we will be targeting a MAJOR release toward the end of the year they are all candidates. Please do add items you are committed to work on to the Roadmap. https://wiki.jasig.org/display/CAS/CAS+Roadmap I would urge us to mostly focus on features that folks are targeting for production deployment or are already in production (LPPE was a good example). I am very weary of phantom requirements. Best, Bill > > Best regards, > Jérôme > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- 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
