Diff for "ReviewerMeetingAgenda"

Not logged in - Log In / Register

Differences between revisions 10 and 291 (spanning 281 versions)
Revision 10 as of 2008-11-26 14:48:16
Size: 6864
Editor: barry
Comment:
Revision 291 as of 2010-05-19 15:40:32
Size: 8684
Editor: henninge
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
`irc.freenode.net`, and are chaired by BarryWarsaw for both the Asia/Pacific (Asia``Pac) and Americas/EU (AMEU) time zone meetings. We use [[https://wiki.ubuntu.com/ScribesTeam/MootBot|MootBot]] to record the meetings. `irc.freenode.net`, and are chaired by BradCrittenden for both the Asia/Pacific (Asia``Pac) and Americas/EU (AMEU) time zone meetings. We use [[https://wiki.ubuntu.com/ScribesTeam/MootBot|MootBot]] to record the meetings.
Line 13: Line 13:
 * Asia``Pac '''Tuesday 02-Dec-2008 0300 UTC - 0345 UTC'''
 * AMEU '''Wednesday 26-Nov-2008 1500 UTC - 1545
UTC'''

You can add new items to the list of proposed items. If they don't make it onto this meetings agenda, they'll most likely get onto the next meeting's agenda instead.
 * AMEU '''Wednesday 19-May-2010 1400 UTC - 1445 UTC'''
* Asia``Pac '''Wednesday 19-May-2010 2130 UTC - 2200 UTC'''

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.
Line 22: Line 22:
 * Merge proposal bugs
   * 245257 - 5 (diffs/bundles)
   * 202000 - 3 (complete diffs)
   * 300462 - 2 (better follow up diffs)
   * 297547 - 2 (CC someone via email)
   * 295156 - 1 (one mail on merge proposals)
   * 297640 - 1 (quote comments in web ui)
   * 297669 - 1 (Approve a mp via email)
   * 301836 - 1 (dashboard - difficult to figure out what to do)
   * 264905 - 1 (access via launchpadlib)
 * If there's time, the old boring script
   * Next meeting
   * Action items
   * Queue status
   * Mentoring update
     * al-maisan looking for a mentor
   * Getting graphs in place before rolling out features (way before) - beuno
 * Agenda
 * Outstanding actions
 * Mentoring update
 * New topics
   * ec2 failures update - bac
   * Reviewer move to Friday? - bac
 * Peanut gallery
Line 44: Line 34:
 * your name, date, reason   * ''yourname, date''
Line 48: Line 38:
 * barry to look into techniques for eliminating back-patching of schema types (avoiding circular imports)  * bac to define new doctest policy regarding what is "testable documentation".
Line 54: Line 44:
 * 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."

 * topic [yourname]
Line 57: Line 59:
 * [[ReviewerMeeting20100505]]
 * [[ReviewerMeeting20100428]]
 * [[ReviewerMeeting20100421]]
 * [[ReviewerMeeting20100414]]
 * [[ReviewerMeeting20100407]]
 * [[ReviewerMeeting20100324]]
 * [[ReviewerMeeting20100317]]
 * [[ReviewerMeeting20100303]]
 * [[ReviewerMeeting20100224]]
 * [[ReviewerMeeting20100217]]
 * [[ReviewerMeeting20100210]]
 * [[ReviewerMeeting20100127]]
 * [[ReviewerMeeting20100120]]
 * [[ReviewerMeeting20100113]]
 * [[ReviewerMeeting20100106]]
 * [[ReviewerMeeting20091125]]
 * [[ReviewerMeeting20091014]]
 * [[ReviewerMeeting20091007]]
 * [[ReviewerMeeting20090930]]
 * [[ReviewerMeeting20090923]]
 * [[ReviewerMeeting20090916]]
 * [[ReviewerMeeting20090909]]
 * [[ReviewerMeeting20090902]]
 * [[ReviewerMeeting20090826]]
 * [[ReviewerMeeting20090819]]
 * [[ReviewerMeeting20090812]]
 * [[ReviewerMeeting20090805]]
 * [[ReviewerMeeting20090729]]
 * [[ReviewerMeeting20090722]]
 * [[ReviewerMeeting20090715]]
 * [[ReviewerMeeting20090708]]
 * [[ReviewerMeeting20090701]]
 * [[ReviewerMeeting20090624]]
 * [[ReviewerMeeting20090617]]
 * [[ReviewerMeeting20090610]]
 * [[ReviewerMeeting20090603]]
 * [[ReviewerMeeting20090513]]
 * [[ReviewerMeeting20090506]]
 * [[ReviewerMeeting20090429]]
 * [[ReviewerMeeting20090422]]
 * [[ReviewerMeeting20090415]]
 * [[ReviewerMeeting20090408]]
 * [[ReviewerMeeting20090318]]
 * [[ReviewerMeeting20090311]]
 * [[ReviewerMeeting20090304]]
 * [[ReviewerMeeting20090225]]
 * [[ReviewerMeeting20090218]]
 * [[ReviewerMeeting20090211]]
 * [[ReviewerMeeting20090204]]
 * [[ReviewerMeeting20090128]]
 * [[ReviewerMeeting20090121]]
 * [[ReviewerMeeting20090114]]
 * [[ReviewerMeeting20090107]]
 * [[ReviewerMeeting20081217]]
 * [[ReviewerMeeting20081210]]
 * [[ReviewerMeeting20081209]]
 * [[ReviewerMeeting20081203]]

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 19-May-2010 1400 UTC - 1445 UTC

  • AsiaPac Wednesday 19-May-2010 2130 UTC - 2200 UTC

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
  • Mentoring update
  • New topics
    • ec2 failures update - bac
    • Reviewer move to Friday? - bac
  • Peanut gallery

Apologies

Please include the date for which you will be unavailable.

  • yourname, date

Outstanding Actions

  • bac to define new doctest policy regarding what is "testable documentation".

Notes

Proposed items

  • 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."
  • topic [yourname]

Rejected items

Summaries of previous meetings

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