So it turns out we can configure the default assignee for JIRA issues to be unassigned. I think this makes more sense for the project and will help keep JIRA more consistent with reality. Unless there are objections I'll go ahead and make this change by the end of the week.
Best, Bill On Mon, Apr 1, 2013 at 3:55 PM, William G. Thompson, Jr. <wgt...@gmail.com> wrote: > I updated JIRA to reflect new proposed schedule: > * RC1 2013-04-29 > * GA 2013-05-31 > > Of course this is all still subject to change, but I do think it would > be good for the project if we cut a release going into the Apereo > conference in June. My preference would be to reschedule items to > 4.1/5.0 if they aren't completed by the RC1 (whenever we decide that > is). > > I also sync'd up 4.0 RC1 and 4.0 issues. Any issue for 4.0 should > also be marked fix-for 4.0 RC1 so that we can track progress on > RC2,3,4 if need be, and still have a full set for the 4.0 release > notes. We currently have 45 of 70 issues resolved. > > The Unicon crew has a bunch assigned and open. We'll be reviewing > those shortly to see if there's anything we might suggest moving to > 4.1/5.0. > > There's also a bunch assigned to Marvin which I suspect is simply > because of the default assignee setting. Marvin, any chance you could > review those and mark them unassigned if you don't plan on getting to > them for 4.0. This would give others, including Unicon, some sense of > what issues are up for grabs. Other suggestions on how best to > proceed? Anyone know if we can we make the default assignee > "unassigned"? > > Best, > Bill > > > > On Sat, Mar 30, 2013 at 5:21 AM, jleleu <lel...@gmail.com> wrote: >> Hi team, >> >> Just my 2 cents in the roadmap. >> >> When I prepared my slides for Devoxx, I spent time thinking about "strengths >> and weaknesses" of CAS. Questions I had at the end of my presentation and >> even after, reassures me in my thinking. >> >> I think that our top priorities for CAS 4.0 should be : >> - front-channel SLO : Marvin will propose something very soon >> - returned attributes on service ticket validation : Robert did a great work >> on CAS 3.0 protocol spec : validation and then implementation are still to >> achieve. >> >> Best regards, >> Jérôme >> >> -- >> 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
