Jump to: navigation, search

Difference between revisions of "DTP PMC Meeting, November 4, 2008"

(New page: ← Back to DTP PMC Meeting Page ==Attendees== *Brian Fitzpatrick *Linda Chan *John Graham *Sheila Sholars *(Brian Payton) ==Regrets== ==Agenda== *Open discussion...)
 
(Action Items)
 
(5 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
*John Graham
 
*John Graham
 
*Sheila Sholars
 
*Sheila Sholars
*(Brian Payton)
+
*Brian Payton
  
 
==Regrets==
 
==Regrets==
  
 
==Agenda==
 
==Agenda==
 +
*When to branch? November 13?
 +
*Status of 1.6.2M1 (if required)
 +
*Microsoft Update
 
*Open discussion
 
*Open discussion
  
 
==Minutes==
 
==Minutes==
 +
*Voted for Galileo to be 1.7, not 2.0
 +
*Voted to move Galileo to JDK 1.5
  
 
==Action Items==
 
==Action Items==
 +
*Find out if we need to decide about 1.7/2.0 = see on deadlines
 +
*IP review for EMF-Ecore - check to see what the process is
 +
*end of release checklist - update versions for 1.6.2M1 -fourth place version changed - possibly leave a comment in the map file to indicate if the version changed - possibly look at releng tool
 +
*need way to remind committers that when they deliver changes, they need to update the plug-in version when necessary (review the plug-in versioning policy)
  
 
==Tabled for Later Discussion==
 
==Tabled for Later Discussion==
  
 
[[Category:Data Tools Platform]]
 
[[Category:Data Tools Platform]]

Latest revision as of 14:59, 4 November 2008

Back to DTP PMC Meeting Page

Attendees

  • Brian Fitzpatrick
  • Linda Chan
  • John Graham
  • Sheila Sholars
  • Brian Payton

Regrets

Agenda

  • When to branch? November 13?
  • Status of 1.6.2M1 (if required)
  • Microsoft Update
  • Open discussion

Minutes

  • Voted for Galileo to be 1.7, not 2.0
  • Voted to move Galileo to JDK 1.5

Action Items

  • Find out if we need to decide about 1.7/2.0 = see on deadlines
  • IP review for EMF-Ecore - check to see what the process is
  • end of release checklist - update versions for 1.6.2M1 -fourth place version changed - possibly leave a comment in the map file to indicate if the version changed - possibly look at releng tool
  • need way to remind committers that when they deliver changes, they need to update the plug-in version when necessary (review the plug-in versioning policy)

Tabled for Later Discussion