in my opinion we do need a release date for the new specification. I recommend we use the same date as for 4.0, as we tag the release in git, right?
Otherwise, it might be worth thinking of moving the protocol dir out into the gh-pages branch as Marvin proposed. Am 12.12.2013 um 17:34 schrieb Jérôme LELEU <[email protected]>: > Hi Robert, > > I'm not sure to understand why we need the release date of the 4.0 in the > protocol spec. > Would you mind enlightening me on this ? > Thanks. > Best regards, > Jérôme > > > > 2013/12/12 Robert Oschwald <[email protected]> > Please note that I will add a new pull request after 355 is merged > and right before release including: > - update the document version to 3.0 (release) > - set the Release Date > > For this, I need a concrete release date from you all. > > > Am 12.12.2013 um 12:47 schrieb Misagh Moayyed <[email protected]>: > >> Update: There are two pending JIRAs that should be the last what's left on >> the list before the next release: >> >> CAS-1284: (protocol doc updates) https://github.com/Jasig/cas/pull/355 >> CAS-1283: (new p3 endpoints) https://github.com/Jasig/cas/pull/375 >> >> Misagh >> > > -- > 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 -- 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
