launchpad development|
Size: 9048
Comment:
|
Size: 8669
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * AMEU '''Wednesday 9-Jun-2010 1400 UTC - 1445 UTC''' * Asia``Pac '''Wednesday 9-Jun-2010 2130 UTC - 2200 UTC''' |
* AMEU '''Wednesday 16-Jun-2010 1400 UTC - 1445 UTC''' * Asia``Pac '''Wednesday 16-Jun-2010 2130 UTC - 2200 UTC''' |
| Line 26: | Line 26: |
| * 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] |
* make lint [deryck] * Using slave stores to speed up your code [bigjools] * ec2 fix update. * bac to discuss moving code out of c/l in AMEU reviewers meeting per thumper's suggestion. |
| Line 49: | Line 40: |
| * 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 |
* bac and abentley to define new doctest policy regarding what is "testable documentation". * flacoste to talk to QA about our QA tracking problem and create a proposal on the mailing list * Bjornt to set a policy on what can live in lib/lp, lib/services, and lib/coop * gary_poster and ursinha to email the list re: orphan branches policy and solution |
| Line 57: | Line 51: |
| * make lint [deryck] * Using slave stores to speed up your code [bigjools] |
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 16-Jun-2010 1400 UTC - 1445 UTC
AsiaPac Wednesday 16-Jun-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
- make lint [deryck]
- Using slave stores to speed up your code [bigjools]
- ec2 fix update.
- bac to discuss moving code out of c/l in AMEU reviewers meeting per thumper's suggestion.
- Peanut gallery
Apologies
Please include the date for which you will be unavailable.
yourname, date
Outstanding Actions
- bac and abentley to define new doctest policy regarding what is "testable documentation".
- flacoste to talk to QA about our QA tracking problem and create a proposal on the mailing list
- Bjornt to set a policy on what can live in lib/lp, lib/services, and lib/coop
- gary_poster and ursinha to email the list re: orphan branches policy and solution
Notes
Proposed items
- topic [yourname]
Rejected items
