[Cosmo-dev] Cosmo trunk development

[Ted Leung]

Now that we have branched for Cosmo 0.6, we have the question of how  
to manage development along the trunk.

  We already know that we are going to have a Cosmo 0.6.1 release.    
This release will be focused on ironing out interoperability problems  
with Cosmo 0.6 and Chandler 0.7a5.   This is some ways out (see  
<http://wiki.osafoundation.org/Projects/PreviewReleaseCountdown> for  
a current best estimate of timelines).   Most of the work for 0.6.1  
will be in the backend part of Cosmo.

In the meantime, we are going to be taking dogfood feedback changes  
to the UI and potentially some changes for a Chandler like dashboard  
in the UI (these may not land in time for 0.7).   The dogfood  
feedback changes will probably either go into Cosmo 0.7 or a Cosmo  
0.6.x (x might even be 1) branch.    We've previously agreed to do  
the dashboard work in a branch.

This means we will have at least 3 parallel lines of development.   A  
branch for Cosmo 0.6.1,  a branch for the dashboard, and the trunk  
(which will become Cosmo 0.7, which is the Preview version of Cosmo).

Should we create the 0.6.1 branch now?   Any other thoughts on ways  
to manage this?

Ted