Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

WTP 2008-11-06

Revision as of 16:08, 6 November 2008 by Unnamed Poltroon (Talk) (Bug List for 3.1)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

WTP Development Status Meeting


Project Leads
Konstantin Y
Tim Y
Nitin Y
Kathy Y
Chuck Y
Kaloyan Y
Raghu Y
Neil Y
David Y
Helen Y
Bob Y
Carl Y
Amy Y
Kate Y
Angel Y
Brad Y
Valentin Y
Gary Y
Nick Y
Chris Y

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

Announcements And Special Reports

  • Minutes:
Eclipsecon 2009 call for participation
DaveC => XSL Tutorial submitted
Thanks Nitin for the old help for new friend doc
Auto IP Log
link to full documentation to the automatic IP Log, also available under project info, eclipse portal page, project leads should bookmark
IPLog flag in bugzilla, change that to a + if someone submits a patch who is not a committer
Kathy: used to use contributed keyword? should use IPLog w/ a + sigh instead
David: Starting now, and back in time for anything over the last few months
last year's contributed
Tim: set the IPLog and + sign on the patch or the bug?
David: most specific thing, should do it on the patch, since patch only has 1 person's name attached to it
Kaloyan: still use contributed?
David: No need to remove if its already there, but no need to keep using it now
Kosta: a committer on 1 subproject contributes to another project where she/she is not a committer on, then should that be marked as well?
David: yes, its at a subproject level
Kathy: where would these be listed eventually? IP log for various subproject?
David: yes that is where it should be listed
Nitin: For sse, its listing login name but not the actual person's name
David: Name optional when sign up for bugzilla id, so it's not actually required, will take that question and try to find out
Tim: Mine is showing up like that too
David: could be timing related, when people became committers or became not committers, will look into that bugzilla id vs name. Will ask around if something could be done there or improve the report
Don't hesitate to ask if you have questions on wtp-dev, the doc is very detailed as well, if can't find who to ask, then David can direct
Gary: what if someone submits a patch, and its not used, fixed it up and used a new one, then what to do?
David: if it is not used should be make obsolete, if using a modified a version then yes okay to count as IPLog+, should also give feedback to the sumitter to better patch submission process
Attendance is way down from previous years, webtools classes was comparable to previous years, so still quite popular and well attended, material is available on the web, link posted
Eclipse Summit
upcoming: Kaloyan is presenting, Cameran for JSF
David compliance will be driven by bugzilla, so can tell milestone by milestone
Gary: who sets these must do and should dos? such as performance, how can we make it a must do?
David: needs a champion on the planning council
Gary: devote a milestone to performance?
David: gets tricky if we start to pick out 1 area and make it a must do, as each project has its own objectives, its hard to dictate somethings encourage for us in WTP first to do it better

WTP Calendar

WTP 3.0.3

10/03 M build
10/17 M build
10/24 RC1 (PMC review starts after RC1, initially one vote)
10/31 RC2 (after RC2, two PMC votes)
11/7 RC3 (after RC3, three PMC votes)
11/14 3.0.3 Release

Build & Smoketest

  • Build
Not yet available
  • Junit
  • Smoketest
Smoketest Results
  • Final Test week next week 11/10
Please update testplan
Focus should be on verifying fixed bugs next week
Only regression bugs found during testing or stopship will be considered by PMC
Test results posted by 3pm EST Friday

Bug Lists for 3.0.3

Blockers & Criticals (~2)
All 3.0.3 Hotbugs (~1)
Current 3.0.3 & 2.0.3 targeted bugs (~2)
In tabular form:
Current 3.0.3 & 2.0.3 targeted bugs (~2)

Fixed Bugs

Web Tools
Number Fixed for 3.0.3 (~159)
Java Server Faces
Number Fixed for 3.0.3 (~0)
Dali JPA Tools
Number Fixed for 2.0.3 (~3)
  • Miinutes
SAP hotbug 251809: will have QA results tomorrow from SAP
David: I'm good once the problem is good
Tim: approve
Chuck: likely to cause problems?
Carl: code is passing through alot, but it is a specific area of fix is isolated
will be checked into the build, while awaiting QA results tomorrow, Kaloyan will send out a note to releng with the results tomorrow. If bad, then will revert

WTP 3.1


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.
New format First draft 9/20, Final copy 10/30


  • Please finish filling in the New and Noteworthy for M3 by Wednesday the 5th
  • org.eclipse.wst.xml.ui will be moving to 1.1.0 when M4 begins, prepare accordingly

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 -> Sept 26 (extra week added so not to overlap maintenance release) (updated)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
3.0.3 Early Maintenance Release Nov 14
M4 -> Dec 19
M5 -> Feb 6
3.0.4 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

  • Build
Awaiting fix for Junit error

Bug List for 3.1

Invalid 3.1 & 2.1 enhancements (~0)
Invalid 3.1 & 2.1 targeted bugs (~0)
3.1M3 & 2.1M3 enhancements (~0)
3.1M3 & 2.1M3 targeted bugs (~5)
3.1 & 2.1 enhancements (~107)
3.1 & 2.1 targeted bugs (~296)
In tabular form:
Current 3.1 & 2.1 targeted bugs (~312)
Blockers & Criticals (~2)
3.1 & 2.1 hotbugs (~0)
  • Minutes:
10 Junit failure in XML encoding after moving up platform dependency. Platform bug opened, they will need to fix for M4, but does not need them to respin M3 for this malformed errorcases, Nick will be commenting out the Junit test for our M3 and referencing the bugzilla
Testplan updates needed by tomorrow 5pm EST to complete testing, still need plans from
Chuck: JEE
Raghu: JSF
Neil: JPA
Angel: Server
Nick: XML
Brad: JSDT
Nitin: New and noteworthy for JSF, mentions to add more information on the common page

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:
Visual Editor => going under initial review, and approval to check code into CVS
XML Security => going through IP review
XQuery => final paper work, done IP review

Build subscription information

Build notification list added: Angel, Nitin, Neil, Raghu
Kaloyan: WTP performance call on Mondays moved to today as a section on WTP Performance
Last meeting defined open action items, listed under WTP performance wiki page
Anyone has any comments on those to note there
Gary: Questions on instruction, running for a development environment?
Kaloyan: Yes for now dev only

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.3 and M3
  • 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


  • Feature exceptions
  • Bug Fixes


  • triage/planning


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

Back to the top