Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

TPTP-PMC-20071205

Revision as of 15:50, 10 December 2007 by Unnamed Poltroon (Talk) (4.5)

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

4.5

Back to the top