[cosmo-dev] Cosmo Engineering Meeting, Thursday, October 24, 2007 2pm PT

[Aparna Kadakia]

Ted,
I am on PTO part of the day tomorrow (after 2:00 PM in fact) so won't  
be able to attend the meeting. Mikeal and Adam will be present from  
the QA team.
We had a small discussion around the churning of the 6 RCs in the QA  
staff meeting as well and Mikeal will be able to fill you in on the  
options we have laid on the table.

Adam will be working on a list of areas where we could use help in  
writing more tests. He has been busy with 0.8 RCs so should be able  
to work on that soon after. Collectively brainstorming on ideas to  
fix this issue is indeed a step in the right direction. Thank you for  
leading the effort. I will await the notes from the meeting to catch  
up on this.

Aparna


Oct 24, 2007, at 4:31 PM, Ted Leung wrote:

> Hi folks,
>
> I'd like to have the Cosmo Engineering meeting tomorrow during the  
> alloted time slot.  The agenda for the meeting is at: <http:// 
> chandlerproject.org/Journal/CosmoMeeting20071025>
>
> I'd like to call attention to the item marked "Release candidate  
> churn".  I took a look at the bugs that triggered the RC builds for  
> Cosmo 0.8.  I've listed them out below:
>
> RC1 - as usual - not driven by bugs.
> RC2 - needed to back out fix for Bug 10527 - web UI was hanging -  
> regression
> RC3 - Bug 11074 - problem w/ dojo build system - regression
> RC4 - Bug 11090 - migration issues, (None dashboard status) -  
> regression
> RC5 - Bug 11094 - Safari - UUID problem, couldn't create items -  
> regression
> RC6 - Bug 11120 - Saving settings not working - tests disabled -  
> regression
>
> Most of these bugs are in unrelated areas, and it seems to me that  
> we ought to have been able to find these bugs in fewer than 6  
> passes.   Also, from talking to Travis, it's clear that some of the  
> problems that we had were rooted in the client site Atompub code,  
> and he's already working on addressing some of the issues that he's  
> found.   I'd like to spend some time talking about other things  
> that we can do to improve our situation.   It doesn't do us any  
> good to finish feature development / bug fixes in 2 weeks, if we  
> have 6RC's worth of regressions.   Possibilities: assigning  
> developers to write Windmill tests for under covered areas, asking  
> developers to run windmill after feature checkins, and I'm not sure  
> what else.    If we can come up with sensible and productive things  
> for developers to do, then I am willing to allocate a substantial  
> portion (up to the entire thing) of the next 2 week release frame  
> to those activities.
>
> I'm not trying to put anyone on the spot here - what I want to do  
> is to find a productive way for all of us to get back to a good  
> release tempo, and I'm willing to spend two weeks of developer  
> effort in order to make that happen, if that is what it takes.
>
> As usual we will be on my bridge:
> 800-391-1709
> 480552
>
> Thanks,
>
> Ted
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev