On Jan 5, 2009, at 7:33 AM, Bennett, Steve wrote: > I know that cosign 2.1.0 is a release candidate, but what is required > for it to be released? > > The date on 2.1.0RC2 is March 17 2008 - are there any significant > issues > that mean that it should not be deployed yet? > > Are there any known upgrade or interoperability issues between > 2.0.2/2.1.0 filters and cosignds? > > I'd like to upgrade from 2.0.2, but I don't want to get laughed at > if it > all goes horribly wrong.
I have a couple more patches to check in, which I intend to do tomorrow. I'm hoping we'll be able to release 2.1.0rc3 later this week, and 2.1.0 itself shortly thereafter. The 2.1.0rc2 cgi has a bug in it that prevents the regexes from matching the appropriate authenticators. The current CVS head fixes it. Here at umich we're running a modified 2.1.0rc2 (which I think is identical to CVS head) in production. That said, you probably want to wait for at least 2.1.0rc3, if not 2.1.0 final. andrew ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
