TPTP Jan 07 face to face

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 Jan 9/10/11 2007

• Deal with current issues
  • 4.4 aka Europa M4 build
    • TPTP builds are ready but the Europa site is not ready.
  • 4.2.2

   * Currently 24 defects targeted to 4.2.2.
   * Project leads will triage the 4.2.2 targeted defects to determine the candidate defects that are required for 4.2.2 and can be completed this week.
   * 4.2.2 will declare Microsoft Vista tolerance (as does the reaming Eclipse projects) instead of Microsoft Vista support.

• • 4.3.1

   *

• any role changes

   * 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
   * Europa packaging categories - who owns
   * Documentation, website, wiki ownership and testing

• 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.

• any project structure changes

   * 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

   *

• 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