Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

2007-07-12

WTP Development Status Meeting 2007-07-12

Attendees

John L, Angel V, Valentin B, Kathy C, Jess G, Bob F, Carl A, Chuck B, Nitin D, Raghu S, David W, Konstantin K, Hoy L, Rob F, Kaloyan R, Larry D, Tim D


Announcements

  • Congratulations to Lahiru Sandakith becoming latest WTP Web Services Committer. (Paper work still in progress).
  • Should we be using the myFoundation portal?
No, not yet, still working on getting that set up correctly for our project.
  • Voting also underway for the nomination of Carl Anderson to WTP JEE Committer.
  • Call for papers ends July 13th for the OS Summit Asia. Note there is a travel and housing stipend and are looking for WTP participation!
  • Eclipse will be moving to Bugzilla 3.0 which features an improved look and feel for bugs, as well as some new features.
  • Change to the Web Service Component Team Lead
Congratulations to Kathy Chan
Thanks to Chris Brealey
  • JPT and JSF please add target milestones for WTP 3.0.
  • We are aware of the committer build page issues and missing 1.5.5 builds. David is investigating 195692.
  • Chris Aniszczyk is organizing a community outreach Bug Day each month. Teams wishing to participate should sign up at this month's wiki page by the 26th.

WTP 1.5.5

WTP Release 1.5.5 Schedule - Remember 2 votes are required for PMC approval for 1.5.5.

July 13 M Build
July 27 M Build
Aug 10 RC1
Aug 17 RC2 (only if needed for blocking bugs or major regressions)
Aug 24
Aug 31 1.5.5 GA
  • If you fix a 1.5.5 bug, please open a separate 2.0.1 bug. I don't think we need a separate 3.0 bug.
  • Build Status
JUnits - No failures.
Please smoke test and update the wiki to declare this week's WTP 1.5.5 build.
  • Please note the 1.5.x releases are temporarily missing from our update site. Users can download the zips as a workaround.
  • Bug lists (WST,JST,JSF)
Invalid Targeted Defects <1.5.5 (~1)
1.5.x Untargeted Blockers/Criticals (~2)
1.5.x Untriaged Bugs (~4)
1.5.5 Bugs for WTP PMC review and approval (~4)
1.5.5 Hot Bug Requests (~0)
1.5.5 Hot Bugs (~3)
1.5.5 Blockers, Criticals (~5)
1.5.5 Remaining Targeted Bugs (~23)
1.5.5 Total Bugs Fixed (~30)
1.5.x Resolved, Unverified (~40)
1.5.x Verified, Not closed (~0)


Europa Information

Community feedback has not been great to say the least, please actively embrace the community and respond to queries.
  • Please continue to contribute to the release notes page.
  • Some orbit bundles are duplicated, with the larger ones coming from the platform because they are signed. The ones from WTP are unsigned and smaller.
  • Here is our current WTP 2.0 Release Scorecard
  • The SDK versions are not available from the Europa update site.
  • A new and fixed 'Eclipse IDE for Java EE Developers' package is available for download.
  • The eclipse-jee-europa-win32.zip is the most downloaded Europa package to date.
  • Install sizes:
Megs Installed Components
45 Eclipse Platform
58 XML (and XSD, DTD) includes +5 meg of prereqs (part of EMF, GEF)
70 WST (non-Java Web Development), no new preq-reqs
116 JST, includes 19 Megs of prereqs: JDT + more EMF
128 JPT, includes 10 Megs of prereqs (Datatools and EMF SDO)
473 All of Europa


  • Please monitor the following sites for WTP related Europa queries:
The eclipse.technology.dali, standard webtools.*, and comp.lang.java.programmer newsgroups
http://developers.slashdot.org/
http://www.javalobby.org/
http://www.theserverside.com/ -- typically the news section
http://www.eclipseplugincentral.com/PNphpBB2+main.html
http://www.eclipsezone.com/eclipse/forums/c5605.html
http://www.jroller.com/
http://forums.devx.com/forumdisplay.php?f=154


WTP 2.0.1

  • Schedule (Proposed)
July 20 M Build
Aug 03 M Build
Aug 17 M Build
Aug 31 M Build
Sept 07 RC1 (PMC approval 2 votes)
Sept 14 RC2 (PMC approval 2 votes)
Sept 21 RC3 (PMC approval 2 votes)
Sept 28 2.0.1 GA


  • Are we clear on branching policy and strategy? Apparently not.  :-) Result of discussion is we will table branching until we have the 3.0 plans in place. Note that JPT has already branched.
All the JST and WST stuff that was part of WTP 2.0 was tagged with a version of R2_0_0. Similarly, JSF and JPT with R1_0_0.
The releng project is branched to R2_0_maintenance, and JSF and JPT are branched to R1_0_maintenance. Please use these branches for your associated plug-ins, respectively.
Investigate not showing web service access errors, David?
Investigate adding section for know bugs and limitations from investigations into access warnings.
  • Build Status
JUnits - J2EE investigating issues with 400 new JUnits added.
No declared build this week. We will start declaring 2.0.1 builds bi-weekly next Friday.
  • Bug Lists
All Remaining 2.0.1 Targeted Bugs (~135)
2.0.1 Hot Bug Requests (~0)
2.0.1 Hot Bugs (~0)
2.0.1 Untargeted Blockers/Criticals (~1)
2.0.1 Blockers/Criticals (~5)
2.0.1 Total JST, WST, JSF Bugs Fixed (~16)
2.0.1 Dali Total Bugs Fixed (~11)
2.0.1 Resolved, Unverified Blockers/Criticals (~2) By Assignee


WTP 3.0

  • Requirements - For information on gathering and defining the requirements for this release, see the WTP 3.0 Requirements Wiki. The goal is get more input and earlier in the cycle than happened in WTP 2.0. The intent is for this to be iterative so that each milestone we are adding and removing as is realistic.
July 17th - Target for publishing the top down major themes with input from the Eclipse Council and the overall structure of the WTP 3.0 Requirements document.
Then components take bottom up approach aligning line items and enhancements in bugzilla with themes. We will review the requirements each meeting in July to keep everyone informed and to come to a general consensus. If any additional discussions need to take place we will have those groups take off line.
July 31st - We will sign off on component leads input and take forward for community review.


  • Jetty Adapter
Jan Bartel, Webtide LLC at janb@webtide.com is planning to contribute a Jetty adapter through the additional server adapters option.


M1

  • M1 Schedule?
July 2007 - August 2007
Monday Tuesday Wednesday Thursday Friday
23
Planning
24
Planning
25
Planning
26
Status Call
Smoke Test
27
Declare I Build
30
Development
31
Development
01
Development
02
Status Call
Smoke Test
03
Declare I Build
06
Development
07
Development
08
Development
09
Status Call
Smoke Test
10
Declare I Build
13
Development
14
Development
15
Development
16
Status Call
Smoke Test
17
Declare I Build
Platform M1?
20
Development
Start component lead change approval
21
Development
22
Development
23
Status Call
Smoke Test
24
Declare I Build
EMF M1?
Write tests and produce FVT driver
27
FVT and Compatibility Tests
28
Defect Verifications
Mustfix defects
29
Defect Verifications
Mustfix defects
30
Defect Verifications
Status Call
Thumbs Up Test
31
Declare WTP 3.0 M1?


  • M1 Themes?
Evaluate non-API use and ensure requests are open if our code cannot be changed.
Fix pre-req ranges where we are API clean.


  • Bug Lists
3.0 M1 Targeted Bugzilla Enhancements (~1)
All Remaining 3.0 Targeted Enhancements (~29)
3.0 M1 Remaining Targeted Bugs (~9)
3.0 M1 Hot Bug Requests (~0)
3.0 M1 Hot Bugs (~0)
3.0 M1 Blockers/Criticals (~0)
3.0 M1 JST, WST, JSF Bugs Fixed (~0)
3.0 M1 JPT Dali Bugs Fixed (~0)
3.0 Untargeted Blockers/Criticals (~1)
3.0 Resolved, Unverified Blockers/Criticals (~0) By Assignee
3.0 Total JST, WST, JSF Bugs Fixed (~3)
3.0 Total JPT Dali Bugs Fixed (~0)


2.0 Debriefing

  • Let's give everyone a chance to share and discuss what worked, what didn't work, and any suggestions for 3.0:
Please continue to update the wiki as you get ideas or suggestions!


Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~109) 40 in J2EE components
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~0)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~567)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3242)
All Resolved, Remind or Later (Graph)
All Resolved, Remind or Later (~58)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~229)
All API Requests (~9)


Working Groups

  • Java EE 5
JEE5 Test Scenarios
When opening related defects, add "JEE5-UC" in the Status Whiteboard


  • Website
Bob F ?


Other business?

Teams Status and Focus for Coming Week

Server Component Team

Datatools (RDB, 1.5.x only)

XML/JSP Component Team

  • Working on fixes for 2.0.1 and 1.5.5.
  • Brainstorming 3.0
  • Ongoing triaging of incoming bug reports

Web Services Component Team

  • Working on fixes for 2.0.1 and 1.5.5.
  • Ongoing triaging of incoming bug reports.

Java EE Component Team

Dali JPA

  • Branched releng and code base for maintenance
  • Checked in several 1.0.1 patches
  • Planning for Dali 2.0

JSF

releng

  • Running Performance and API tests

Performance

Known Issues
  • The baseline test needs to be rerun each week to eliminate false "hiccups" in performance.
Action Items
  • Improve the UI readability and cohesiveness of the output result pages
  • Improve the actual tests. Why do some take so long? Why do some results fluctuate? Why do some have 160% performance degradations? Are the tests even still valid?
  • Allow committers to reliably and efficiently run perfomance suites in the workspace before checking in code
  • Add JSF and JPA performance JUnits


API Violations Review

Visit latest build for current API violations.
Action 1 = For any violation, open a bug to request API or fix code to not use internal discouraged access. An example is using images or labels from other plugins, these should be copied into your plugin. Also, using internal classes instead of the API interfaces.
Action 2 = If you do have a clean plugin of API violations/discourage access, switch prereq ranges wide so you can react to small version number changes without issue.
Action 3 = To be able to develop with discouraged access enabled, we need to update plugin's .classpath rules. Should we turn off defaults to expose all warnings to get a quicker resolution?


References

  • 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 3.0 Smoke Results Page
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


Back to WTP Meeting Archives
Back to Web Tools Wiki Home

Back to the top