TPTP-PMC-20090408

Logistics

• Attending: Paul, Oliver, Kathy, Harm, Chris

4.6

Are the P1 bugs for 4.6 getting resolved?

• We seem to be pretty on track for P1 bug status. Test took on a bunch
  • Paul wants to revisit whether all P1s can be covered by end of I2 development

Regarding possibly dropping a P1 236477...

• memory statistics view exceed 100%
• Further examination shows it only happens in isolated scenario.
• Seems to happen during some updates of the view rather than being consistently incorrect
• Not really critical for consumer for this pass. want to go to P2 instead of P1

PMC approval mode discussion

Kathy mentions that till now, during PMC approval mode, template has been filled in a fwded to PMC mailing list for +1 -1 via email

• Easy to lose track of mailing list discussion (historically)
• Kathy mentions that we can put template into bugzilla and copy PMC members to go into and approve.
  • Benefit is to log discussion in bugzilla itself.
  • Original reason for mailing list was PMC list would allow others subscribed to PMC mailing list to come in and comment on these late items
    • Some folks might see the items and want to then go and watch the defects
    • This is pretty subtle however and as far as we know has not really generated much additional feedback over the years

Harm noted that pasting in the 6 reviewer names might be a bit error prone

• We discussed having thosenames in the template to make it easy for developer to copy/paste.

PMC members will one get notification on the bug for folks to vote

• Should appear as an "action requested" in PMC members inbox so PMC members are aware that there is a specific action item requested.
• Votes will be logged and normal bugzilla updates sent.

We clarified that this discussion is only regarding PMC approval mode (i.e., for late checkins), not for changing priorities from 1->2 which still needs to be on lists and in PMC discussion.

Kathy would like to add to template an item about the "nature of the fix" (e.g., scope of code changed, etc.)

• More information is always good but there was some discussion that this is what developers should already be putting into the template under the complexity of the fix section.

Misc

New dialin numbers are needed for following meetings.

• AR to Chris

Kathy had some ideas about making it easier to keep up to date IPlog (tracking stuff by non-committers)...

• There are bugzilla fields to fill in that something was a non-committer contribution
• Project lead should use it if submission by someone not a committer yet. Helps with finishing release when IPlog is created.
• Action item to leads to go thru 4.6 stuff and populate this for stuff submitted by non-committers
  • Scenario was discussed where someone becomes a committer. Stuff done during a contributor phase should still be tagged even if person becomes committer prior to 4.6 release.

Builds moving to IBM pretty much good to go except for IPF.

• Chris to give update next week on shipment progress

Solaris sparc AC patch available under 268860

• Please review.

Kathy requested an update needed from Yunan regarding attach/detach defect 194081

• Chris to probe Yunan