Engineering Meeting - Tuesday February 7th, 2006

Agenda

• 0.6.1
• 0.7 planning
  • Phases to the release
  • Bugzilla: how should product team tag/flag for 0.7 prioritization?
  • Assigning performance bugs
  • Ownership/drivership: are we clear about who owns what in the dev team for 0.7?
  • Performance: next steps
• Any stalled dev threads that need to be jumpstarted?
  • Functional and unit tests: any next steps?
  • Sheriff: next steps required here?

0.6.1

All 0.6.1 bugs resolved. No more changes to the build. We started the build this morning and it's in QA hands right now. Some bugs found that need to be triaged.

Non code actions:

• Update the launch page (Pieter and Sheila)
• Update the ReadMe^? with the updated bugs (Pieter and Sheila)
• Update the Wiki release check list (Heikki)
• Update the download link (Bear)
• Announce to lists and Blog (Pieter)

0.7 planning

Phases to the release

Sheila and others trying to identify 4 rough large phases. Will post the list with this as a proposal. Asking for feedback so that we can identify milestones (phases are not milestones though...).

Bugzilla: how should product team tag/flag for 0.7 prioritization?

Use which field for the phase? Propose to use Whiteboard Status.

We are using the the WS for tenet buckets.

Add the Phases to the WS

The WS is also used for SWAG

Priority to be reviewed: Philippe to review Sheila's prioritization email and comment.

Assigning performance bugs

Keeping the non met bugs open. Open new bugs for the ones for which we are changing the target.

Keep those bugs on hold right now? OK for new features / new targets but we should address perf regression as soon as possible. Heikki to send the decision to the list.

Ownership/drivership: are we clear about who owns what in the dev team for 0.7?

List of components to review and attach owners. Some tasks unclear like "Notifications and Collections".

Performance: next steps

Sheila and Katie to communicate the new test and targets to Heikki (discussion going on on the lists).

Any stalled dev threads that need to be jumpstarted?

Functional and unit tests: any next steps?

Aparna to follow up with devs when new features are implemented so that we make sure unit and functional tests are written.

Decision : Add list of planned functional tests to specs.

Sheriff: next steps required here?

Devs have been working on failing tests. Bear working on tools. Heikki to write the new sheriff schedule. Functional test failure on Linux being worked on by QA.

Katie to send a last call email on the "Sheriff and build tool" thread.