[Cosmo-dev] Cosmo 0.6 as first dogfood release

[Ted Leung]

On Jan 2, 2007, at 5:43 PM, Brian Moseley wrote:

> On 1/2/07, Katie Capps Parlante <capps at osafoundation.org> wrote:
>
>> - Any bug that corrupts calendar data from the UI is a "showstopper"
>> - Any bug that crashes the server from the UI is a showstopper
>> - Any bug that blocks the casual collaborator workflow is a  
>> showstopper
>> - Interop bugs with Chandler sharing/eim/morse code are showstoppers
>>
>> - The team will hold the release until all known showstopper bugs  
>> are fixed
>> - The team will spin a 0.6.1 release and push it up to osaf.us if
>> showstopper bugs are found shortly after the release
>> - The team will consider minor features/larger fixes for 0.6.1 (or
>> 0.6.x) if they make a big difference for casual collaborator  
>> usability
>
> what about interoperability with other programs? i'm especially
> concerned about how data shared between cosmo and chandler fares when
> it is consumed or produced by third party apps (for example, items
> created by chandler, shared to cosmo, then subscribed to and edited in
> sunbird or evolution).

What should the the appropriate level of priority for these kinds of  
bugs?  Should they be "drop everything and fix this" like the other  
showstoppers or can we deal with them on a less urgent basis?

Ted