launchpad development|
Size: 8323
Comment:
|
Size: 8684
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * AMEU '''Wednesday 21-Apr-2010 1400 UTC - 1445 UTC''' * Asia``Pac '''Wednesday 21-Apr-2010 2130 UTC - 2200 UTC''' |
* AMEU '''Wednesday 19-May-2010 1400 UTC - 1445 UTC''' * Asia``Pac '''Wednesday 19-May-2010 2130 UTC - 2200 UTC''' |
| Line 26: | Line 26: |
| * Reduction of negation preferred over "common case first" in if statements? [henninge, jtv] | * ec2 failures update - bac * Reviewer move to Friday? - bac |
| Line 38: | Line 39: |
| * henninge to update the style guide regarding multi-line parameters in function defns and calls. * bac to get input on proposed community reviewer and committer policy and announce it on the list. |
|
| Line 45: | 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." |
|
| Line 50: | Line 59: |
| * [[ReviewerMeeting20100505]] * [[ReviewerMeeting20100428]] * [[ReviewerMeeting20100421]] |
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
