We typically follow the uPortal one which I believe was based off of Apache (which we follow for everything else :-)).
When we set "4.0" as our SAML goal and decided to release the required changes earlier rather than later, that's how we came up with the current numbering versions. If we're going to call it 4.0, then I'd prefer that we scope the Service Management changes in and get all of our major API changes in at once. Most of the API changes that were going to be in 3.5 were API changes that we as developers write against (even if others were also able to write against then. I.e. SessionStorage) On Tue, Nov 9, 2010 at 4:12 PM, Marvin Addison <[email protected]>wrote: > > At 4.0 seems to be consistent with the uP Release Strategy: > > https://wiki.jasig.org/display/UPC/Release+Strategy assuming we are > > still follow it. > > Thanks for pointing that out, Bill. I know different projects have > different standards for version number changes, but all the ones I've > seen agree that major API changes are major number increases. If we > don't already have a document that describes our criteria for version > changes, we should either draft one or follow guidelines from another > project (uPortal seems fine). > > 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
