[Cosmo-dev] Problems subscribing to the Office Calendar

Aparna Kadakia aparna at osafoundation.org
Wed Mar 7 20:39:46 PST 2007


see my comments inline..

On Mar 7, 2007, at 4:39 PM, Ted Leung wrote:

> We currently have a pair of bugs open which impact Chandler  
> dogfooder's ability to subscribe to the office calendar.  This a  
> very serious problem since Chandler dogfooders are wiping their  
> Chandler repositories frequently.
>
> The bugs in question are:
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=8303>
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=8304>
>
> The current assessment is that the problem is due to a few bugs in  
> iCal4j, particularly in respect to the Calendar class's handling of  
> equals().
>
> So where do we go from here?  I think there are a few questions  
> that need answering before we can figure out what to do:
>
> 1. Is iCal4J really the problem?  If so, what is the right fix  
> (asking for a fix upstream, patching ourselves, patching Cosmo code)?
> 2. Is the problem severe enough to warrant a Cosmo 0.6.0.1 release  
> and accompanying osaf.us upgrade?

I think so. Also, I think the same issue is manifesting in other  
personal calendars shared on osaf.us which we are using for our  
tests. I fear some of the recent errors we have been seeing in  
Chandler are related to data corruption in the test calendars  
published on osaf.us. That's just a guess right now.

> 3. If 2 is correct, how much QA will we need to do and does QA have  
> the bandwidth to do so?
Since it is a patch release being rolled out on production, certain  
minimum QA process is certainly required.
1. put the release candidate on qacosmo, verify bug 8304
2. run full automated regression and functional test suite (this is  
half days work since some of the tests will have to be reworked to  
make them compatible with the old UUIDs which were changed in 0.7)
3. test chandler+cosmo interoperability (mostly manual)

This should take us about a day.

Plus whatever time Jared takes to setup staging and running the  
upgrade tests against that.

>
> If you have answers or opinions on any of these three questions,  
> please reply.
>
> Ted
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev



More information about the cosmo-dev mailing list