[Cosmo-dev] Cosmo 0.6 as first dogfood release

[Katie Capps Parlante]

Hi all,

So 0.6 is going to be the first "dogfood" release of Cosmo's UI, 
usable-enough for internal OSAF users and similarly adventurous souls. 
(We've been dogfooding Cosmo as a server for many months now, of course).

It is a pretty exciting milestone -- I know I will be trying out Cosmo 
to share calendars with my favorite casual collaborator (my spouse).

I wanted to make sure I'm on the same page as everyone on what "dogfood" 
will mean, in terms of release decisions, how bugs are triaged, etc. My 
working assumptions:

- 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

The overall goal would be to have our internal dogfooders *really using* 
cosmo for the office calendar and other casual collaborator use cases. 
I'd expect that this might require a little more work for stabilization, 
and a little more work to get multiple releases out on osaf.us. The 
benefit of course is to have our first real users of the UI giving 
useful feedback and shaking out the kinks.

Let me know if my assumptions are different from the rest of the team, 
or if they need to be refined to be more clear/accurate.

Cheers,
Katie