3.2 schedule / freeze

Cantor, Scott cantor.2 at osu.edu
Fri Oct 30 00:46:48 EDT 2015


On 10/29/15, 10:54 PM, "dev on behalf of Daniel Fisher" <dev-bounces at shibboleth.net on behalf of dfisher at vt.edu> wrote:



>I know Marvin is working on a few CAS issues that came to our attention recently. +1 for pushing the code freeze date by a week.

I think the biggest was fixed Thursday, but there may be others.

There are some smaller things I'd still like to consider for inclusion plus be able to get the logout work finished (as much as it's going to be in this release), so I guess I'll +1 that. I didn't want to ship so late in November, but better to get it cooked, especially with all the churn in the Jenkins builds.

I don't think we need a call, it sounds like there's enough to do to justify waiting a week.

I would like to see if we can get the builds stablized by tomorrow or Monday at the latest.

-- Scott



More information about the dev mailing list