Jump to: navigation, search

Difference between revisions of "WTP 2008-09-18"

(Bug List for 3.1)
(Bug List for 3.1)
 
(4 intermediate revisions by 2 users not shown)
Line 8: Line 8:
 
{| border="1"
 
{| border="1"
 
|+ Project Leads
 
|+ Project Leads
|width="80%"|Konstantin ||  
+
|width="80%"|Konstantin || Y
 
|-
 
|-
|Tim ||  
+
|Tim || Y
 
|-
 
|-
|Nitin ||  
+
|Nitin || Y
 
|-
 
|-
|Kathy ||  
+
|Kathy || Y
 
|-
 
|-
|Chuck ||  
+
|Chuck || Y
 
|-
 
|-
|Kaloyan||  
+
|Kaloyan|| Y
 
|-
 
|-
 
|Raghu ||  
 
|Raghu ||  
 
|-
 
|-
|Neil ||  
+
|Neil || Y
 
|-
 
|-
|David ||  
+
|David || Y
 
|-
 
|-
|Helen ||  
+
|Helen || Y
 
|-
 
|-
 
|Philippe ||  
 
|Philippe ||  
Line 33: Line 33:
 
{| border="1"
 
{| border="1"
 
|+ Committers
 
|+ Committers
|width="80%"|Bob ||  
+
|width="80%"|Bob || Y
 
|-
 
|-
|Carl ||  
+
|Carl || Y
 
|-
 
|-
|Dave ||  
+
|Dave || Y
 
|-
 
|-
|Phil ||  
+
|Phil || Y
 
|-
 
|-
 
|Naci ||  
 
|Naci ||  
 
|-
 
|-
|Larry||  
+
|Larry|| Y
 
|-
 
|-
|Amy||  
+
|Amy|| Y
 
|-
 
|-
|Kate||  
+
|Kate|| Y
 
|-
 
|-
|Angel||  
+
|Angel|| Y
 
|-
 
|-
|Brad||  
+
|Brad|| Y
 
|-
 
|-
|Valentin ||  
+
|Valentin || Y
 
|-
 
|-
|Gary ||  
+
|Gary || Y
 
|-
 
|-
 
|Paul||  
 
|Paul||  
Line 62: Line 62:
 
{| border="1"
 
{| border="1"
 
|+ Friends
 
|+ Friends
|width="80%"|Nick ||  
+
|width="80%"|Nick || Y
 
|-
 
|-
 
|Gilbert ||  
 
|Gilbert ||  
Line 115: Line 115:
  
 
*Minutes:
 
*Minutes:
 +
:2 bugs still targeted to 302, Konstantin will look into retargeting
 +
:smoketest to be complete today and 302 build to declare
  
 
== WTP 3.1 ==  
 
== WTP 3.1 ==  
Line 176: Line 178:
  
 
*Minutes:
 
*Minutes:
 +
3.1
 +
: 3.1 planning in the new format
 +
: First draft 9/20
 +
: Final copy 10/30
 +
: Link to new format will be posted
  
 
== Other business ==
 
== Other business ==
Line 208: Line 215:
  
 
==== Server Tools====
 
==== Server Tools====
- Last week we update the landing website, to include revised defect queries and new format
 
(http://www.eclipse.org/webtools/server/)
 
 
- Completed plan for 3.1
 
  
 
==== Web Services/WSDL ====
 
==== Web Services/WSDL ====

Latest revision as of 13:36, 18 September 2008

WTP Development Status Meeting

Attendees

Project Leads
Konstantin Y
Tim Y
Nitin Y
Kathy Y
Chuck Y
Kaloyan Y
Raghu
Neil Y
David Y
Helen Y
Philippe
Committers
Bob Y
Carl Y
Dave Y
Phil Y
Naci
Larry Y
Amy Y
Kate Y
Angel Y
Brad Y
Valentin Y
Gary Y
Paul
Friends
Nick Y
Gilbert

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports

WTP 3.0.2

Aug 29 - M build
Sept 5 - RC1 (All changes after RC1 require ONE PMC approval votes)
Sept 12 - RC2 (All changes after RC2 require TWO PMC approval votes)
Sept 17 - RC3 & final build (updated)
Sept 23 - GA (updated)
  • Build & Smoketest
M-3.0.2-20080918035538
Smoketest has bee issued


Bug Lists for 3.0.2

PMC Approval Summary List
Blockers & Criticals (~3)
All 3.0.2 Hotbugs (~0)
Current 3.0.2 & 2.0.2 targeted bugs (~2)
In tabular form:
Current 3.0.2 & 2.0.2 targeted bugs (~2)


Fixed Bugs

Web Tools
Number Fixed for 3.0.2 (~81)
Java Server Faces
Number Fixed for 3.0.2 (~9)
Dali JPA Tools
Number Fixed for 2.0.2 (~10)
  • Minutes:
2 bugs still targeted to 302, Konstantin will look into retargeting
smoketest to be complete today and 302 build to declare

WTP 3.1

Planning

WTP 3.1 Project Plan

Two issues came up when discussing the planning process

  1. How to handle "future" milestone target? Turns out we have discussed and documented this before, see WTP_Bugs, Workflow and Conventions#The meaning of "Future" milestone target.
  2. How can we better incorporate bugs-to-fix in 3.1 planning? Subsequent to meeting, I suggested that leads/committers should set the 3.1 milestone target for bugs that ideally should be fixed in 3.1, to help "prime the pot". For example, nearly all voted on bugs and "major" bugs should be so marked. I've added more bugzilla queries to WTP 3.1 Project Plan to assist.

Schedule

Adjusted schedule, based on Platform's proposed schedule.

Normally, our milestone are one week after the Platform's delivery. Exceptions noted below.

3.0.1 Early Maintenance Release Aug 15
M1 -> Aug 22 (extra week added so not to overlap maintenance release)
3.0.2 Coordinated Maintenance Release Sep 24
M2 -> Oct 3 (extra week added so not to overlap maintenance release)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
M4 -> Dec 19
M5 -> Feb 6
3.0.3 Coordinated Maintenance Release Feb 25
(EclipseCon March 23-27)
M6 -> Mar 20 Feature Complete, API Freeze, UI Freeze, NLS, Accessibility
M7 -> May 8 Performance tuning, documentation, bug fixing
RC1 -> May 22 Serious bugs only, focus on stability.
RC2 -> May 29 WTP will likely not participate in an RC2, based on feedback from last year that RC2 came too soon, needed more fixing, less testing
RC3 -> Jun 5 Very serious bugs only.
RC4 -> Jun 12 Very very serious bugs only.
RC5 -> Jun 19 Hopefully no changes from RC4. Prepare web pages, update sites, etc.
GA -> Jun 24

Build & Smoketest

  • Waiting for current build to complete
  • smoketest will be issued once build is available

Bug List for 3.1

Invalid 3.1M1 & 2.1M1 enhancements (~0)
Invalid 3.1M1 & 2.1M1 targeted bugs (~0)
3.1M2 & 2.1M2 enhancements (~4)
3.1M2 & 2.1M2 targeted bugs (~9)
3.1 & 2.1 enhancements (~96)
3.1 & 2.1 targeted bugs (~227)
In tabular form:
Current 3.1 & 2.1 targeted bugs (~227)
Blockers & Criticals (~3)
3.1 & 2.1 hotbugs (~0)
  • Minutes:

3.1

3.1 planning in the new format
First draft 9/20
Final copy 10/30
Link to new format will be posted

Other business

WTP UI Walkthroughs
Thre New Incubator proposals
Visual Editor for XML (VEX)
bug 169810
XML Security Tools Proposal
bug 243106
XQuery Proposal
bug 225394
  • Minutes:

Teams Status and Focus for Coming Week

Performance Team

The minutes of the meetings are posted. Next meeting is next Monday same time. See details on the wiki page: WTP Performance Tests

Source Editing

  • Ongoing triaging of incoming bug reports
  • Working on 3.0.2
  • Deciding overall themes and plan for 3.1

Server Tools

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing and verifying bugs.

Java EE

JEE Status Meetings

Dali JPT

  • JPT 2.0
    • Working on:
      • EclipseLink support
      • Bugs for M7
      • Performance

JSF

  • Feature exceptions
  • Bug Fixes

releng

  • triage/planning

References

In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
  • Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well
  • This Week's Smoke Test Results
WTP Smoke Test Results R30
Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
PMC Candidate Review Request Checklist - See the updated PMC Review document with attention to the "How To Prepare a PMC Defect Candidate" section
Adopter Migration Information for WTP 2.0 - Please add any details for your component.
  • Website
Documentation on Setting up your system for Web Tools Web site development and Using Web Tools Phoenix PHP templates is on the wiki at Web Tools Web Site Development.
  • Bug Day
Monitor and participate in Bug Day if you would like.
Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in IRC
Current WTP Bug Day bugs (~53)


Project Meta data, for Project leads, especially, see "information about ..." from your subproject web page left nav bar.
Go to Foundation Portal
Login with committer ID
Click on "[maintain] Project Info meta-data"
Changes coming to IP Log management (more automated, but more for Project Leads to do?): See Development Resources/Automatic IP Log