Chandler Engineering Meeting - August 17th, 2006

Agenda

• Alpha4 : Let's check how we are doing against the schedule (Philippe - 10 min)
• Alpha5 and beyond : We need to identify what we are going to stuff in those releases earlier than we did with the past alpha (we now have specs and a better idea of what we want for beta so we should be able to do that). Discussion on what needs to happen to get there (Philippe, Sheila - 10 min)
• Build : We're having issues with virtualization solutions (for the wx build). Heikki and Bear to update the group on this (10 min)
• Interns : We need to think about landing of intern stuff. How should we handle that in SVN? Incorporate to build? Test? This opens the more general issue of how we handle 3rd party parcels. Open discussion (10 min)
• Release Management : There was some confusion on what the status of alpha3 was among people outside the Bug Council. We need to think about formalizing this (especially the end game) so that everyone understands where we stand, especially when things slip. (Heikki - 10 min)

Minutes

Alpha4

• apps team seems fine timewise
• sharing format design might get done, but not implementation - dependent on both chandler and cosmo
• sharing urls will also change
• what is really shaping the release is the dashboard, with some aspects of stamping and sharing

Alpha5 and beyond

• current plan needs to be redone
• main features: user defined attributes and labeling, email
• sticky plan update next week (Sheila)
• detailed specs done by mid-September (Sheila)
• we want to start filling the bugzilla milestones from now to beta to get better visibility of our future
• some cosmo hosted service discussion; we need to QA against the real hosted service at some point, but probably not until 2007

Wx tbox

• vmware time sync problems; seems we have a workaround
• also have an imac to be used for this
• Plan is to have all these operational within 2 weeks

Landing intern's code, proposed plan:

• Darshana (NLP) should be mainlined, alpha5
• Travis (IMAP) should probably be mainlined, alpha4
• Ashkan (usage tracking) should be mainlined, alpha4
• Markku (i18n) is already in
• Ernesto (contacts) should be an optional egg; need maintainer, functional tests; plan on how it fits in beta (design team?)
• Xun (statistics, tagging) should remain in his sandbox for now
• Vinu (cosmo)
• Berook (cosmo, qa oaf)
• Ed (scooby)

Release management

• Heikki & Philippe to create release plan checklists (actually improve on the current Chandler and Cosmo checklists)

-- PhilippeBossut - 16 Aug 2006