3.2 schedule / freeze

[Brent Putman]

On 10/29/15 5:24 PM, Cantor, Scott wrote:
> I can go either way on this, but if we want to try and freeze tomorrow I'll probably be working up until the deadline.

I probably would also.  And I have tickets to see  Bill Nye The Science
Guy tomorrow night. :-(


>
> I'm probably 80% done getting single logout for SAML plugged in, which means it's silly not to include it even if we have to delay. The testing for that will definitely push into next week though, so if freeze really means freeze and not "feature freeze", I'd need a week more.

I'm probably a little better on the delegation stuff, maybe 98%. What's
left is mostly just cleaning up Javadocs and giving everything a last
once-over to make sure I haven't missed anything.

But I did want to dot i's and cross t's on the HttpClient, TLS socket
factory and SOAP client stuff I did a few months back - just
double-checking the new stuff that's been added before we commit to it.

And if we were going to freeze tomorrow, I'm pretty sure I'm going to
rip all the recent metadata indexing stuff out for now, since it's not
really finished and I don't want to commit to the APIs.  If we delay,
esp another full week, I *might* instead be able to finish the remaining
bits and convince myself that it could ship in 3.2.  We're not using it
yet, so it doesn't matter either way.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20151029/12f22bff/attachment.html>