Skip to main content
Jump to: navigation, search

TPTP-PMC-20071205

Attendees

  • Present:
    • Paul Slauenwhite
    • Oliver Cole
    • Alexander Alexeev
    • Alex Nan
    • Joanna Kubasta
    • Alan Haggarty
    • Guru Nagarajan
    • Harm Sluiman
  • Absent:
    • Chris Elford - vacation

Previous Week

Status of Last Week's Action Items

  • AI: Project leads to send TPTP-InactiveCommitter-FormLetter to each inactive committer for their project see here for committer lists:
    • Monitor: Outstanding.
    • Test: Note has been sent. Wait for two weeks before removing inactive committers.
    • Platform: Outstanding.
    • Trace: Guru spoke to some Intel committers but there are more on the list to contact.
  • AI: Project leads to review the Component reorganization WIKI
    • Monitor: Outstanding.
    • Test: Done.
    • Platform: Outstanding.
    • Trace: Outstanding.
  • AI: Since the 4.5 Plan has been approved, project leads to update the priority (P1) and keyword (plan - if resources are available) for the enhancements.
    • Monitor: Done.
    • Test: Done.
    • Platform: Done.
    • Trace: Done.
  • AI: Project leads to Revise the description for your project's planned enhancements in the 4.5 Plan. Note, related enhancements may be integrated into one row.
    • Monitor: Outstanding.
    • Test: Done.
    • Platform: Outstanding.
    • Trace: Outstanding.
  • AI: Everyone to review the EclipseCon 2008 submissions and reply to my comments by replying to this message or directly to the submissions at EclipseCon site (->Category Test and Performance->Search).
    • Only Chris replied to Paul's summaries.
  • AI: For Guru, need testing overhead estimates for the 4 manual tests that are in Trace.
    • Outstanding.
  • AI: Leads to go read/comment on test automation documents
    • Monitor: Outstanding.
    • Test: Done.
    • Platform: Outstanding.
    • Trace: Outstanding.
  • AI: Leads. Weekly milestones should reflect at the very least the targeted completion weeks for every targeted enhancement and defect.
    • Monitor: Done.
    • Test: Done.
    • Platform: Done.
    • Trace: Done.
  • AI: Each lead needs to be especially aware of schedule given breaks and plan out how to accomplish test passes/etc.
    • (note) Paul tried to make sure test pass 1 would happen before bulk of holidays hit.
    • Monitor: Done.
    • Test: Done.
    • Platform: Done.
    • Trace: Done.

Action Items

  • Outstanding action items from last week to be addressed for next week.
  • Guru/Alex A. and Alex N to close on ownership/management of BtM/Trace.Execution component (defects and features) under the trace project and notify the BtM committers so they can report status to Guru and attend the weekly Trace project call.
  • Trace project (Guru/Alex A.) to update weekly schedule with cross dependences and weekly deliverables for the iteration.

4.5

  • The 4.5 builds are broken due to the refactoring required for defect 200138.
    • Alex is working with Joel on resolving the problems.
    • Joel will announce the I4 TP1 candidate before EOD for committers to smoke their components in preparation for TP1.
  • I4 TP1
    • Guru has concerns about testing resources.
      • There is sufficient overlap with the Platform Project components to handle the shortage.
      • Alex A. will start attending the Platform Project weekly call.
    • If we have a candidate before EOD for committers to smoke their components, can we start TP1 on Monday:
      • Monitor: Yes.
      • Test: Yes.
      • Platform: Yes.
      • Trace: Yes.

Profiling

  • Harm tried one of the profiling use cases and experienced several issues. He documented his concerns in a WIKI.
  • We will not aggressively solicit lead users other than Harm until Harms issues/concerns are addressed.
  • Due to constrained resources, may need to remove planned 4.5 defects and enhancements to contain this work.

Weekly Schedule

  • Paul added a legend to marked slipped and completed deliverables.
  • Has each project updated the schedule with their cross dependencies?:
    • Monitor: Yes.
    • Test: Yes.
    • Platform: Yes.
    • Trace: No.
  • Has each project updated the schedule with their weekly deliverables and status?:
    • Monitor: Yes.
    • Test: Yes.
    • Platform: Yes.
    • Trace: No.
  • Slippages:
    • Monitor: Some have slipped (mostly defects) and have been marked slipped.
    • Test: Some have slipped (mostly defects) and have been marked slipped. No concerns except EMMA (no time remaining in the I4 development cycle to prepare for using during TP1).
    • Platform: No update.
    • Trace: No update.

Back to the top