On Mon, Apr 8, 2013 at 3:30 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: > +1 for the process outline generally. I have some concerns about target dates. > >> * Community Review/Feedback - April 8th - April 20nd
The initial proposed dates reflected a desire to have a final protocol spec rev by RC1. However, I'm not sure this is actually required in this case. It probably is reasonable to address issues in CAS4RC1 and the protocol spec revision throughout the RC testing phase since they are mutually dependent on a small but important issue (<cas:attributes>). Here's a revised proposed schedule for the protocol revision release process: * Declare CAS3.0 Protocol Revision as Release Candidate Status on April 29th (same date as CAS4RC1) * Community Review/Feedback/Testing against CAS4RC1 and CAS clients (April 29th - May 31st) * Committer/Contributer Consensus Vote May 31st Thoughts? Best, Bill > > May not be enough time for client maintainers. If we want them to > carefully review the specification and consider the impact to their > project, which I hope is the intent, then it's likely not enough time. > I think one of the design goals of the spec, backward compatibility, > is particularly important for client maintainer feedback. I'm fairly > pessimistic it's achievable in some clients where the XML parsing libs > are weaker (mod_auth_cas), but maintainers' thoughtful feedback is far > more valuable. > > M > > -- > 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
