Diff for "ReviewerMeetingAgenda"

Not logged in - Log In / Register

Differences between revisions 300 and 392 (spanning 92 versions)
Revision 300 as of 2010-06-09 12:52:14
Size: 9048
Editor: bac
Comment:
Revision 392 as of 2010-12-15 15:37:44
Size: 8752
Editor: bac
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * AMEU '''Wednesday 2-Jun-2010 1400 UTC - 1445 UTC'''
 * Asia``Pac '''Wednesday 2-Jun-2010 2130 UTC - 2200 UTC'''
 * AMEU '''Wednesday 22-Dec-2010 1500 UTC - 1545 UTC'''
 * Asia``Pac '''Thursday 16-Dec-2010 0000 UTC - 0030UTC'''
Line 24: Line 24:
 * Mentoring update
 * New topics
   * Schedule shuffle
   * Ursinha's comments on orphaned commits after last week's meeting. [henninge]
     She would prefer to have a bug attached to each commit but has realized that
     there are commit types that do not reflect a defect and therefore will not have
     a bug. The first objective of QA tags is to make sure that a bug's fix will be
     verified.

    So the rules could be:
     * "If a commit will need QA, it must be linked to a bug."
     * "Orphaned commits are those that should have a bug but don't."

   * Reminder about policy for reviews and landings from external contributors. Making sure the "lander" is recorded is a Good Idea. [henninge]
 * Mentat update.
   * Salgado (ui)
   * StevenK (code)
   * Benji (code)
   * JCSackett (code)
   * MRevell (ui)
 * New items
   * Should reviewers expect the review template to be used? - abentley
   * Integrating test timing into reviews, recap. -bac
Line 49: Line 43:
 * bac to define new doctest policy regarding what is "testable documentation".
 * sinzui to talk to QA about our QA tracking problem and create a proposal on the mailing list
 * new proposal for integrating the Arch Guide into reviews. --bac
 * bigjools to update the style guide for api_.
Line 56: Line 50:
 * topic [yourname]
 * make lint [deryck]
 * Using slave stores to speed up your code [bigjools]
Line 62: Line 53:
Line 63: Line 55:

 * [[ReviewerMeeting20101020]]
 * [[ReviewerMeeting20101013]]
 * [[ReviewerMeeting20101006]]
 * [[ReviewerMeeting20100901]]
 * [[ReviewerMeeting20100804]]
 * [[ReviewerMeeting20100721]]
 * [[ReviewerMeeting20100707]]
 * [[ReviewerMeeting20100630]]
 * [[ReviewerMeeting20100616]]
 * [[ReviewerMeeting20100609]]

Agenda of the next Launchpad review team meeting

Launchpad review team meetings are held on #launchpad-meeting on irc.freenode.net, and are chaired by BradCrittenden for both the Asia/Pacific (AsiaPac) and Americas/EU (AMEU) time zone meetings. We use MootBot to record the meetings.

The purpose of the meetings is to coordinate Launchpad code reviews, and particularly to ensure that emerging issues with the review process are addressed - such as getting people to take on tough reviews, keeping the latency down, etc.. Blockage in reviews leads to blockage in Launchpad code landings.

The next Launchpad review team meeting will be held at this time:

  • AMEU Wednesday 22-Dec-2010 1500 UTC - 1545 UTC

  • AsiaPac Thursday 16-Dec-2010 0000 UTC - 0030UTC

You can add new items to the list of proposed items. If they don't make it onto this meeting's agenda, they'll most likely get onto the next meeting's agenda instead.

Agenda

  • Roll call
  • Agenda
  • Outstanding actions
  • Mentat update.
    • Salgado (ui)
    • StevenK (code)
    • Benji (code)
    • JCSackett (code)
    • MRevell (ui)
  • New items
    • Should reviewers expect the review template to be used? - abentley
    • Integrating test timing into reviews, recap. -bac
  • Peanut gallery

Apologies

Please include the date for which you will be unavailable.

  • yourname, date

Outstanding Actions

  • new proposal for integrating the Arch Guide into reviews. --bac
  • bigjools to update the style guide for api_.

Notes

Proposed items

Rejected items

Summaries of previous meetings

ReviewerMeetingAgenda (last edited 2011-01-24 20:30:18 by bac)