[Cosmo-dev] Problems subscribing to the Office Calendar

[Ted Leung]

So based on this and Aparna's message, it looks to me like we should  
do the 1 line fix and get some kind of checkpoint to QA  so they can  
get going.  Concurrently with the testing, we ought to send a patch  
up stream to ical4j.

Any other concerns on this before we start down this path?

Ted

On Mar 7, 2007, at 7:06 PM, Randy Letness wrote:

> Ted Leung wrote:
>> 1. Is iCal4J really the problem?  If so, what is the right fix  
>> (asking for a fix upstream, patching ourselves, patching Cosmo code)?
>
> There are a couple ways of fixing this.  We can fix the ical4j  
> code, or we can fix it in Cosmo code (should be a one-line fix).  I  
> would suggest fixing in our code as its quick and easy and we are  
> in the middle of moving away from using custom ical4j code. I've  
> already submitted an ical4j bug so hopefully it gets fixed soon and  
> we don't have to worry about this in 0.6.1. (I can also submit a  
> patch).
>
>> 2. Is the problem severe enough to warrant a Cosmo 0.6.0.1 release  
>> and accompanying osaf.us upgrade?
>
> If we don't fix the problem, we will continue to see corrupted  
> events.  I think it needs to be fixed to prevent further corruption.
>
>> 3. If 2 is correct, how much QA will we need to do and does QA  
>> have the bandwidth to do so?
>>
>
> QA should be minimal, just verifying basic functionality.
>
> -Randy
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev