[Cosmo-dev] Cosmo 0.6.1.1 release
jared at wordzoo.com
Tue Jun 26 14:41:42 PDT 2007
Summary: We're going to release a Cosmo 0.6.1.1, incorporating r4733,
and push it to Chandler Hub. Bear, could you please proceed with the
Background: A rare but usage-blocking issues was found on Chandler Hub
related to the length of EXDATE parameters supported by Cosmo 0.6.1.
Enough people would like to see this fixed that the Cosmo release
meeting decided to release a Cosmo 0.6.1.1 release which addresses only
this specific issue.
The bug is #9537 (which is unfortunately marked as staff-only because it
has some private information attached). The patch extends the length of
the EXDATE info allowed to 32K; the change is Cosmo r4733 by bcm.
I haven't heard any objections to proceeding with a Cosmo 0.6.1.1;
please raise them if you have any.
Also, if you have other features from trunk that you think should be
backported to 0.6.1.1, please let us know. I had previously said there
was a content-length issue in 0.6.1 we might consider, but there is
actually no such issue.
There's a couple different ways to proceed with patching the Hub, but
the best for this situation is to branch Cosmo in Cosmo SVN for 0.6.1.1
and have QA validate the new branch.
Bear, could you branch a Cosmo 0.6.1.1 tree and apply r4733 to it, then
produce a checkpoint release? Not a rush, next couple of days. Please
flag and stop if r4733 doesn't apply cleanly.
Adam and I will determine whether testing this branch on qacosmo will
interfere inappropriately with Cosmo 0.7-pre testing. If they are going
to step on each other, and given that I need to see 0.6.1.1 validated
against existing production data, we may instead validate 0.6.1.1 using
a hub-hosted instance (but go through the same validation steps we would
More information about the cosmo-dev