On Tue, Nov 9, 2010 at 2:34 PM, Marvin Addison <[email protected]>wrote:
> I've spent the last several days studying the 3.5 API and it confirms > some concerns I've had about scope of change. Everything is changing: > I owe you a bottle of vodka or something then since I'm still changing them every couple of day :-) I've got a new one I want to discuss on list tonight that I'll send out after work. > > - Terminology > - Package layouts > - Core component interfaces > > I think when I initially supported the current roadmap, > https://wiki.jasig.org/pages/viewpage.action?pageId=28574039, I was > lacking a concrete picture of the scope of change involved in 3.5. > It's simply going to be a big release, and it's worth reconsidering > our numbering. I think it's reasonable to simply bump our version > numbers in the roadmap such that 3.5 goes to 4.0 and the subsequent > releases follow in minor number increases, 4.1, 4.2, 4.3. I believe > the numbers matter -- bumping the major number signals a big change, > which is exactly what we're planning. > The reason we hesitated from calling it "4" was because originally we wanted the SAML2 support to be 4. However, as reality sets in I'm fine with calling this version 4 assuming the steering committee goes for it. Should we follow up on the steering committee list since other members might be filtering cas-dev into a folder and reading it sporatically? > > M > > -- > 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 > -- 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
