launchpad development|
Size: 6759
Comment:
|
Size: 6996
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * Asia``Pac '''Tuesday 23-Dec-2008 0300 UTC - 0345 UTC''' * AMEU '''Wednesday 17-Dec-2008 1500 UTC - 1545 UTC''' |
* Asia``Pac '''Wednesday 25-Feb-2009 2300 UTC - 2345 UTC''' * AMEU '''Wednesday 25-Feb-2009 1500 UTC - 1545 UTC''' |
| Line 22: | Line 22: |
| * Last meeting of the year? * Peanut gallery (anything not on the agenda) |
|
| Line 26: | Line 24: |
| * Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica) * Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary * Merge proposals and cover letters (barry) * Peanut gallery (anything not on the agenda) |
|
| Line 32: | Line 33: |
| * your name, date, reason | * your name, date |
| Line 36: | Line 37: |
| * barry to look into techniques for eliminating back-patching of schema types (avoiding circular imports) | * abentley to experiment on storm base class * barry to add `field_id` to coding guideline |
| Line 38: | Line 40: |
| * flacoste to work on API reviewer cheatsheet | * flacoste to work on API reviewer cheat sheet |
| Line 44: | Line 46: |
| * Don't forget to add find-entry-uri rules when exposing new stuff in the API. See [[https://launchpad.canonical.com/API/StyleGuide#Update%20the%20XSLT%20stylesheet|API Style Guide >> Update the XSLT stylesheet]]. -- ''allenap'' | * your topic, your name |
| Line 49: | Line 51: |
| * [[ReviewerMeeting20090218]] * [[ReviewerMeeting20090211]] * [[ReviewerMeeting20090204]] * [[ReviewerMeeting20090128]] * [[ReviewerMeeting20090121]] * [[ReviewerMeeting20090114]] * [[ReviewerMeeting20090107]] * [[ReviewerMeeting20081217]] |
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 BarryWarsaw 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:
AsiaPac Wednesday 25-Feb-2009 2300 UTC - 2345 UTC
AMEU Wednesday 25-Feb-2009 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.
Agenda
- Roll call
- Action items
- Mentoring update
Reviewers to enforce bug<->branch linking for all non-trivial branches (intellectronica)
Determine official preference, if any, of Storm usage: And(expr, expr) vs. expr & expr, Gary
- Merge proposals and cover letters (barry)
- Peanut gallery (anything not on the agenda)
Apologies
Please include the date for which you will be unavailable.
- your name, date
Outstanding Actions
- abentley to experiment on storm base class
barry to add field_id to coding guideline
barry to add pretty() functions to reviewers docs
- flacoste to work on API reviewer cheat sheet
Notes
Proposed items
- your topic, your name
Rejected items
