Please add agenda items here:

• 1.6 release status
  • Status of reported bugs (mailing list & Trac)
    • George's reported acq bugs
    • Repke's Vandelay attempts (might just be "no support for that yet")
    • … ?
  • OpenSRF - we need to cut an OpenSRF release to match Evergreen 1.6 (but wait… shouldn't that be tested first? OH NOES!)
  • Translations - put out a call after 1.6.0, roll translations into 1.6.1?

• Release process
  • miker's model of daily builds, automated testing, with each subsequent release cut directly from trunk?
  • DVCS model of feature development in separate branches, with merges to trunk only when the feature has stabilized?
    • Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code)

• Bug tracking and QA
  • Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness?
  • Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad

• Future development
  • What's shaking in the near future?
  • Any long term projects that we need to start laying the groundwork for now?