On Mon, Apr 8, 2013 at 3:36 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: >> Last week the Unicon crew reviewed JIRA items that were assigned to us >> to make sure we could meet the RC1 deadline of April 29th. > > In light on the ongoing discussion about timeline w/r/t CAS protocol > specification approval, that target date is fairly unreasonable. > You're allotting 3 days between protocol sign off and RC1. The RC > should be feature complete, so it would need to implement the final > protocol spec. I'm don't see how that could be done in that time > frame.
The 3.0 protocol rev has very modest goals and mostly is simply documenting behavior already implemented in CAS3 and various clients. The only JIRA issue I'm aware of that is contingent on the protocol spec rev is CAS-1283, which is well in hand, and a trivial addition. > > I move to bump the timeline by one month or some other reasonable > period of time. I'm much more interested in features and finesse more > than soft dates. What features do you have in mind that are dependent on the 3.0 protocol rev? I can't think of any other than CAS-1283. Best, Bill > > 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
