Engineering Meeting - Tuesday February 16th, 2006

Agenda

• 0.6.1 update? Download info? Anything?
• 0.7 planning
  • Phases and Alphas
  • Status of bug triage, prioritization, component ownership for 0.7
  • What should be the non-code release goals for 0.7 alpha releases?
  • What server (ie: Cosmo build) are the alpha releases going to run against?
• Any stalled mailing list threads that need to be jumpstarted?

Phases and Alphas

• Last call on gen proposal (Katie will send to the list)
• First call on priliminary milestone schedule (Heikki will send to the list)
• Stake in the ground proposal for milestone dates based on these 2 month targets
• We need to be able to create some targets in bugzilla
• Once we do more scoping we can determine if these dates/schedule makes sense
• Phase 0 will start at the end of Feb
• Using alphas instead of milestones with egg compatible version numbering

Status of bug triage, prioritization, component ownership for 0.7

• Triage is done
  • We have more bugs than at the beginning of 0.6
  • We could look at triaging out a number of these
  • Sheila can go and add a few bugs for the calendar dogfood items that aren't currently logged
  • We will wait until we understand the features for the phases and we can defer some bugs that clearly don't fit
• Prioritization we have agreement
• Component ownership - give people a few days to comment - set a date for last call
  • Katie will do a last call tonight for this
• Bear is finishing the work to run the functional tests on tinderbox - aparna will send an email with setup info and status

What should be the non-code release goals for 0.7 alpha releases?

• download link on landing page would not change
• public - for feedback and qa
  • blog it
• we have some second level pages from the main page we could use....
  • how to get involved page
• news section on the main page
• html page
• Sheila will send out a proposal to the design and dev lists
• Heikki noted that the For Devs link in the chandler landing page doesn't actually point developers to anything they can get their hands on.
  • send something to the list
  • should we log this in bugzilla also. create a documentation:web component for this.

What server (ie: Cosmo build) are the alpha releases going to run against?

• We don't know what the right solution is.
• Any instance of Chandler should be backwards compatible to previous Cosmo versions.
• Any milestone/alpha should work with Cosmo Demo
• It seems like Cosmo 0.3 should work with Chandler 0.6.
  • What are the dependencies?
  • When are things going to break?
  • How does our strategy change over the course of the release?
  • Assuming that you have an upgrade path for you calendar data for each milestone?

Any stalled mailing list threads that need to be jumpstarted?

• Last call for phasing proposals
• Force this stuff into the 0.7 planning page - updates
• People should scan the "keeping users data" thread
• Last call for alpha proposal