[cosmo-dev] 0.9.0 update

[Mikeal Rogers]

+1

On Nov 14, 2007, at November 14, 200710:16 AM, Jared Rhine wrote:

> A recap of our 0.9.0 status.
>
> We have a final build of 0.9.0.  It has not been announced to lists  
> and the blog.
>
> We discovered there was a significant performance regression for  
> some operations with Cosmo 0.9.0, to the point that we rolled-back  
> the Hub.
>
> How should we set priorities, in particular with Ted mostly  
> unavailable this week?
>
> Most devs are already into a high-urgency performance-review phase.
>
> I suggest the following for priorities:
>
> * Leave the tarball and tag in place; it's not really hurting anyone  
> right now.  Assume we're doing a 0.9.1 release fixing this specific  
> issue; today if it works out.
>
> * Do a all-hands-on-deck sort of thing for characterizing and fixing  
> the performance regression with /atom requests.  Defer any other  
> specific milestone, like 0.10 branching/code-complete until we have  
> a grip on this situation and probably an updated 0.9 pushed to Hub.   
> Fixes from this work go into 0.9 branch.
>
> * Tell Travis to go ahead with putting-the-A-back-in-Ajax work to  
> make our XHR calls not block.  That work can go into 0.9 branch if  
> it's completed early.
>
> * Developers not tied up in the above continue work on 0.10 updates  
> to trunk.
>
> * We see if Ted checks his email by tomorrow, then reassess.
>
> I don't think any of the above is too controversial (maybe the leave  
> 0.9.0 in place and Ajax updates to 0.9 branch), but thought it'd be  
> good to recap and especially see if there's other stuff we ought to  
> be doing.
>
> -- Jared
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev