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

Difference between revisions of "DTP PMC Meeting, September 30, 2008"

(Agenda)
Line 13: Line 13:
 
**If we're switching to JDK 1.5, that's going to require a branch long before 11/5. There will be a fair amount of fixing that needs to be done.
 
**If we're switching to JDK 1.5, that's going to require a branch long before 11/5. There will be a fair amount of fixing that needs to be done.
 
**As for the API refactoring, it was decided last night that the Connectivity API refactoring isn't required for this release. However, I'm still hopeful that the SQL Editor UI/non-UI refactoring will occur. And depending on the degree of change, it may be an API-breaking change and require a 2.0 vs. 1.7 designation.
 
**As for the API refactoring, it was decided last night that the Connectivity API refactoring isn't required for this release. However, I'm still hopeful that the SQL Editor UI/non-UI refactoring will occur. And depending on the degree of change, it may be an API-breaking change and require a 2.0 vs. 1.7 designation.
 
+
*(John) Discussion of consolidated servers view [https://bugs.eclipse.org/bugs/show_bug.cgi?id=247934 BZ247934]
 
*Open discussion
 
*Open discussion
  

Revision as of 11:53, 30 September 2008

Back to DTP PMC Meeting Page

Attendees

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

Regrets

Agenda

  • Decide on JDK level (looks like JDK 1.5 for the build platform)
  • Decide on Branch date for Galileo (first milestone we're really concerned with is M3, which is dated 11/5/2008 for +1 projects)
    • If we're switching to JDK 1.5, that's going to require a branch long before 11/5. There will be a fair amount of fixing that needs to be done.
    • As for the API refactoring, it was decided last night that the Connectivity API refactoring isn't required for this release. However, I'm still hopeful that the SQL Editor UI/non-UI refactoring will occur. And depending on the degree of change, it may be an API-breaking change and require a 2.0 vs. 1.7 designation.
  • (John) Discussion of consolidated servers view BZ247934
  • Open discussion

Minutes

Action Items

Tabled for Later Discussion

Back to the top