Sure thing. I did just account for the comment on the pull. I am hoping that we can proceed to merge by late Friday evening and work on the next RC this weekend.
Misagh ----- Original Message ----- From: "Jérôme LELEU" <lel...@gmail.com> To: cas-dev@lists.jasig.org Sent: Thursday, December 26, 2013 6:43:09 AM Subject: Re: [cas-dev] CAS Protocol v3 Status Hi, Thanks for your work during Christmas ;-) I'm in line, except one remark... Best, Jérôme 2013/12/24 Misagh Moayyed < mmoay...@unicon.net > Pending pull: https://github.com/Jasig/cas/pull/380 Misagh From: "Jérôme LELEU" < lel...@gmail.com > To: cas-dev@lists.jasig.org Sent: Monday, December 23, 2013 7:48:59 AM Subject: Re: [cas-dev] CAS Protocol v3 Status Hi, I just merged the fix for CAS-1403. Though, there is one new issue regarding the logout request. Waiting for the associated JIRA... The RC3 should be cut after this bug has been fixed also. Thanks. Best regards, Jérôme 2013/12/18 Misagh Moayyed < mmoay...@unicon.net > <blockquote> Great. I am happy to volunteer and give RC3 a shot once more. So lets sort of put this out to the team: The proposal is to proceed with an RC3 first, preferably by the upcoming weekend and then a GA in the later part of January. (I am assuming that RC3 would also include a fix for the latest kyro serilization issue that Jérôme reported on another thread.) Does this sound reasonable to everyone? Misagh From: "Jérôme LELEU" < lel...@gmail.com > To: cas-dev@lists.jasig.org Sent: Tuesday, December 17, 2013 9:11:06 AM Subject: Re: [cas-dev] CAS Protocol v3 Status I have nothing against an earlier schedule if we can make it... 2013/12/17 Misagh Moayyed < mmoay...@unicon.net > <blockquote> RC3 sounds good, though I think we can cut it earlier. Practically we are ready to put together RC3 as early as this weekend perhaps, allow a couple of weeks and then a GA by say January 21 st ? Misagh From: Jérôme LELEU [mailto: lel...@gmail.com ] Sent: Tuesday, December 17, 2013 12:39 AM To: cas-dev@lists.jasig.org Subject: Re: [cas-dev] CAS Protocol v3 Status Hi, Using the same date makes sense. Though, the protocol spec won't change from now. So I wouldn't be annoyed to have a prior date for the spec release. Regarding the CAS 4.0 release, the main question we need to address is : do we need one more RC before the final release ? I tend to say yes. So, in that case, I would plan a RC3 at the beginning of Juanary and the final release at the beginning of February, let's say monday, the 3th February. What do you think ? Best regards, Jérôme 2013/12/12 Robert Oschwald < robertoschw...@googlemail.com > 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 < lel...@gmail.com >: 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 < robertoschw...@googlemail.com > 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 < mmoay...@unicon.net >: 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 cas-dev@lists.jasig.org as: lel...@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: robertoschw...@googlemail.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: lel...@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: mmoay...@unicon.net 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: lel...@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: mmoay...@unicon.net 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: lel...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev </blockquote> -- You are currently subscribed to cas-dev@lists.jasig.org as: mmoay...@unicon.net 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: lel...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev </blockquote> -- You are currently subscribed to cas-dev@lists.jasig.org as: mmoay...@unicon.net 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
