launchpad development|
Size: 7152
Comment:
|
Size: 7225
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * AMEU '''Wednesday 18-Mar-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 18-Mar-2009 2230 UTC - 2315 UTC''' |
* AMEU '''Wednesday 08-Apr-2009 1500 UTC - 1545 UTC''' * Asia``Pac '''Wednesday 08-Apr-2009 2230 UTC - 2315 UTC''' |
| Line 17: | Line 17: |
'''NOTE: NO MEETINGS 25-MAR OR 01-APR 2009''' |
|
| Line 23: | Line 25: |
| * Action items | |
| Line 24: | Line 27: |
| * Action items | * Dogtests (intellectronica) * Code must be used once or more to land (excluding tests) (intellectronica) * Avoid refactoring both code and tests in the same branch (intellectronica) |
| Line 34: | Line 39: |
| * gary_poster to add `getStore()` as an alias for `_get_store()` | |
| Line 37: | Line 41: |
| * bigjools to take crack at helper functions for backpatching schemas to avoid circular imports |
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:
AMEU Wednesday 08-Apr-2009 1500 UTC - 1545 UTC
AsiaPac Wednesday 08-Apr-2009 2230 UTC - 2315 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.
NOTE: NO MEETINGS 25-MAR OR 01-APR 2009
Agenda
- Roll call
- Peanut gallery (anything not on the agenda)
- Action items
- Mentoring update
- Dogtests (intellectronica)
- Code must be used once or more to land (excluding tests) (intellectronica)
- Avoid refactoring both code and tests in the same branch (intellectronica)
Apologies
Please include the date for which you will be unavailable.
- your name, date
Outstanding Actions
- flacoste to look into storm/sqlobject result set compatibility
gary_poster will check to see if there's a bug open for adding a hook to bzr send, and submit one if there isn't
thumper to open bug on webservice pagetests globs problem
- flacoste to work on API reviewer cheat sheet
Notes
Proposed items
- your topic, your name
Rejected items
