[Cosmo-dev] Cosmo 0.5 Planning

[Bobby Rullo]

On Aug 24, 2006, at 3:30 PM, Ted Leung wrote:

> The summary of today's Cosmo meeting is now available <http:// 
> wiki.osafoundation.org/bin/view/Journal/ServerMeeting20060824>
>
>
> The majority of the meeting focused on the timing of integrating  
> the Hibernate prototype.  The goal of the discussion was to explore  
> possibilities so that a decision could be made once Bobby and  
> Priscilla were available.
>
> Brian Moseley reported that the progress on the Hibernate prototype  
> has been very rapid and that it looks like Randy at Simdesk will  
> have plenty of availability to work on the Hibernate stuff.   He  
> believes that it is about 3 weeks worth of work to get to a Cosmo  
> which is using the merged codebase and Hibernate instead of  
> Jackrabbit/JCR.
>


If this is indeed the case(that it would only take about three  
weeks), I'd say let's go straight for a Hibernate/Merge release -  
skipping a "Merge" release w/o Hibernate work. Otherwise we have to  
do a bunch of JCR work that gets thrown away.

> Concerns/comment from key stakeholders:
>
> Matthew Eernisse was concerned that he might be blocked from doing  
> UI work if we decide to do the merge and integrate Hibernate all in  
> one big bang.   Brian said that it was probably about a day's worth  
> of work to put in some mock objects or stubs that would return  
> dummy data that would allow Matthew to keep going.
>

I am/was concerned about Matthew being blocked as well, but I think  
we can stub stuff out in a reasonable way so that he has enough to  
work with. Matthew, I can help with the work of making a "mock" cosmo  
server in javascript if you need me to.

> Ted Leung propsed that maybe we ought to split 0.5 into milestones,  
> the way that the desktop team used to.   That would give  
> cosmo-0.5M1 which would contain the merged codebase, cosmo-0.5M2  
> which include Hibernate and  cosmo-0.5 which would include the UI  
> features currently scheduled for 0.5.   The 0.5M label would  
> indicate that the build is riskier than just a 0.5 build, but it  
> would also be a defined build which QA could run a full battery on.


I like the idea of milestones, but not the ones ted proposed, since  
the first one would again require new JCR work which I think we  
should avoid like a particularly nasty variant of bubonic plague. I  
was thinking more like:

	cosmo-0.5M1 - Hibernate work. No new features, no merge.
	cosmo-0.5M2 - Merge w/ Hibernate. TAFKAS* is fully functional, with  
no new features, just the 0.2 feature set.
	cosmo-0.5 - New Features for TAFKAS (Stuff from Scooby 0.3 spec)

Bobby


*TAFKAS = The App Formerly Known As Scooby