[Cosmo-dev] Summary of Cosmo meeting August 24, 2006

[Priscilla Chung]

So I just want to confirm that I prefer splitting out 0.5 into  
milestones. I want to make sure after each significant milestones,  
the release candidate is given to QA for testing. Please note a when  
I say significant milestone, it does not mean a significant release  
candidate.

I just want some clarification about the hibernate work. Perhaps this  
has been discussed on the list? If so, could someone please point me  
to the e-mail thread that explains what it is. That would be great.

In layman's terms what is hibernate specifically and how does it  
improve performance or scalability? Why is this important to do for  
beta?

I think I am having trouble gauging the importance of technical  
features. I'm not arguing if this specific feature needs to be done,  
but I need to prioritize how technical features and product features  
fit into planning releases and timelines. The whole group (not just  
the technical team) needs to understand what these features bring in  
a way that lets us prioritize technical features users never "see"  
with respect to product features more visible to end users.

For example:
+ If hibernate speeds up Chandler by 800% today, then yes, its a very  
good thing to do.
+ If the benefits of hibernate only kick in when we have 2000  
concurrent requests, it may be putting the cart before the horse.  
2000 concurrent requests might happen for 5 minutes a day when we  
have 50,000 registered users.

One last thing relates to the naming of the release candidates. Does  
anyone use 'M' for their releases? Do we want to start following the  
desktop naming conventions and start calling it Alphas/Betas or do we  
want to continue using 0.5.1, 0.5.2, etc. In either case I want to  
make sure we follow conventions of what the developer community is  
already accustomed to.

-Priscilla

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

> 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20060828/6ed175c8/attachment.htm