* Meeting 2010-09-07
  * Agenda: https://wiki.ubuntu.com/TechnicalBoardAgenda?action=recall&rev=309
  * The Board will organize a regular review of user feedback on brainstorm.ubuntu.com according to the proposal described at  https://lists.ubuntu.com/archives/technical-board/2010-September/000493.html
  * The Application Review Board proposed by Jono Bacon in https://lists.ubuntu.com/archives/technical-board/2010-September/000483.html was waved through informally, to bootstrap the application review process. We will re-evaluate in six months.

 * Meeting 2010-09-21
  * Chair: Martin
  * Attendees: Colin Watson, Kees Cook, Scott James Remnant
  * Guests: Jamie Strandboge

  * Review of Actions
   * Martin to follow up with Kees on-list (re: Chromium security updates) -- '''DONE'''
   * Matt to implement brainstorm reviews as proposed  -- '''DONE'''
    * Martin added this as a permanent topic to the agenda, together with the next due date
   * Matt to respond to jono re: application review board  -- '''DONE'''

  * [[https://lists.ubuntu.com/archives/technical-board/2010-September/000506.html|SRU microrelease exception for bzr]]
   * Requirement: Run selftests during package build to catch architecture specific regressions, and catch problems early
   * Run tests on installed package as part of SRU verification
    * '''ACTION:''' Martin Pitt to ask Martin Pool about self test instructions on installed system
    * '''ACTION:''' Kees to add bzr self test to qa-regression-testing project
   * Under those conditions, the request was unanimously approved
    * '''ACTION:''' Martin add to StableReleasePolicy

  * Chromium security updates  
   * Discussion has shown that a general SRU exception is the only viable way
   * It is not realistic to do any serious testing on these, since updates are released so fast; updates need to happen pretty much "blindly"
   * This makes it rather inappropriate for main/default install, but as an opt-in in universe the current experience with the recent Chromium SRUs showed that the process is working
   * In case of new build dependencies: in general they should be bundled, but for some of them it is okay to update the system package (e. g. gyp, and perhaps libvpx); this is a case-by-case decision

  * No new community bugs to look at

  * Next chair: Mark Shuttleworth