Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

TPTP Jan 07 face to face

Revision as of 16:45, 9 January 2007 by Paulslau.ca.ibm.com (Talk | contribs) (→‎Agenda topics January 9/10/11, 2007)

When a call in is active the number will be

Conference ID: 6044164

Dial in Local number: 416-343-2622

Toll-free Dial-in number: 1 866-516-6489

if you want to call in and the line is silent or inactive, e-mail Harm and sluiman@ca.ibm.com

Agenda topics January 9/10/11, 2007

  • Current Issues
  • Role Changes
    • Joanna is proposed to assume the Platform.Execution(Execution) and Platform.Execution.Framework (Execution: Framework) components. The current component owner(s) will nominate Joanna to assume ownership.
    • The build componet will be expanded to include release engineering and web site management.
    • Project leads require CVS privileges for updating the TPTP website (e.g. TPTP Matrix). The PMC/PG approves the following project leads to have CVS privileges to the TPTP web site (http://dev.eclipse.org/viewcvs/index.cgi/www/tptp/?root=Eclipse_Website):
      • -Paul Slauenwhite
      • -Dave Smith
      • -Joanna Kubasta [coordinated with committer nomination]
      • -Guru Nagarajan
    • AG will determine the Europa packaging categories.
    • A committer is required to own the TPTP product documentation (including translating and TVT) and web site documentation (including the WIKI) to reduce the documentation defect backlog, reviewing (e.g. consistency checking) and testing (e.g. spelling, links and grammar).
    • The owner of the componet described by the product documentation will be responsible for the technical review of the documentation once per release (post UI freeze).
  • Housekeeping
    • To cleanup the TPTP Matrix, the following components have been approved to be removed from the TPTP Matrix and Bugzilla:
      • Test.UI (n/a)
      • Test.UI.Charting (Charting)
      • Test.Analysis (Analysis rule)
      • Platform.Execution.Choreography (Execution: Choreography) [org.eclipse.tptp.choreography plug-in is deprecated]
      • Trace.Analysis (n/a)
      • Trace.Execution (Execution: Probe instances)
      • Monitor.UI.CustomizedStatsView (Customized Stats View)
    • Committer matrix will be made dynamic (as prototyped by Hubert last year) based on CVS and Bugzilla.
    • Project leads need to update each project's space on the TPTP web site. Each project's space should be current based on the current features, architecture and user interface. This information should drill down to more detailed functional and architectural information.
  • Project Structure Updates
    • Create a samples/examples componet per project to include the Eclipse-based samples/examples shipped with the TPTP run-time/SDK. The project leads will be the componet leads for these components.
    • Package all of the sample code/projects used at presentations and demonstrations (e.g. conferences) on the TPTP web site packaged as downloadable Eclipse projects/plug-ins.
    • Create and maintain a shared repository of donations from the user community hosted but unsupported by TPTP (e.g. http://www.eclipse.org/tptp/home/project_info/general/contribute_or_feedback.html). For example:
      • GLA rules
      • Static analysis rules
      • Probes
      • BIRT report templates
      • Symptom databases
  • 2006 in Reflection
    • Discussion of IBM's post mortem of TPTP 4.3.
      • Project leads will ensure new test cases for all new defects/enhancements.
      • Project leads will schedule and monitor peer reviews.
      • Committers need to adhere to the project schedules, incrementally check-in code to CVS and continual regression testing.
      • TPTP will investigate running performance benchmarks using SPEC jAppServer (http://www.spec.org/jAppServer/). Each member company of TPTP can use SPEC jAppServer for evaluating the performance impact of TPTP.
      • The Trace project will investigate using PIN for code coverage of TPTP's native code.
      • The Test project will discuss how the Trace project's JVMTI test infrastructure can be integrated with the Test tools.
      • The documented process for defect approval in shutdown mode is:
        • All defects require 1) Project Lead and 2) PG approvals (e-mail on the tptp-pmc@eclipse.org mailing list). Each approval request must be accompanied by a completed stop ship template (http://www.eclipse.org/tptp/home/documents/process/development/stop_ship_template.html) which is included in the defect as well. If the Project Lead has approved the defect, the request is forwarded to the PG by the Project Lead for approval. The defect will be considered approved as soon as one additional PG member votes +1. Any PG member may vote -1 vote which will negate all +1 until there is a resolution by the PMC.
      • This process will be added to the TPTP web site after 4.3.1. This process is followed during the following points of a release:
        • Last week of development in a full release iteration.
        • Last iteration in a full release.
        • All iterations in a maintenance release.
      • Valentina will query the project committers for suggestions on architectural issues they want to address during the weekly AG call. This meeting will be used for:
        • Demonstrations
        • Architectural updates
        • Peer reviews
        • Investigations
  • review each of the project feed backs on what can be done better and what was great
   *
   * propose use of TPTP wiki for discussion and minutes but not as a substitute for other controlled forums.
  • 2007 1H resource planning
   *
  • assess contribution levels and determine what is supportable. Perhaps new approaches are needed
   *
  • assess future maintenance streams
   *
  • defect backlog plans by project
    • Test
   *
    • Monitoring
   *
    • Trace
   *
    • Platform
   *
   *IAC
  • 4.4 enhancement status
    • Stage 1
   *
    • Stage 2
   *
   * Emma integration
  • close on 4.4 plan
   *


  • other topics
    • foundation level conformance and quality testing framework
Retrieved from "https://wiki.eclipse.org/index.php?title=TPTP_Jan_07_face_to_face&oldid=22446"

Back to the top