- 1 WTP Development Status Meeting
- 2 WTP Calendar
- 3 WTP 3.0.1
- 4 WTP 3.1
- 5 Other business
- 6 Teams Status and Focus for Coming Week
- 7 References
WTP Development Status Meeting
Announcements And Special Reports
- Smoketest request issued, please complete smoketest by 3 PM Friday, at latest
Bug Lists for 3.0.1
- Blockers & Criticals (~12!)
- All 3.0.1 Hotbugs (~1)
- In tabular form:
- Current 3.0.1 & 2.0.1 targeted bugs (~150!)
- WOW! Congratulations!
- Web Tools
- Number Fixed for 3.0.1 (~230!)
- Java Server Faces
- Number Fixed for 3.0.1 (~1?)
- Dali JPA Tools
- Number Fixed for 2.0.1 (~30!)
- Adjusted schedule, based on Platform's proposed schedule.
- 3.0.1 Maintenance Release Aug 15
- M1 -> Aug 18
- 3.0.2 Maintenance Release Sep 24
- M2 -> Sep 26
- M3 -> Nov 7
- M4 -> Dec 19
- M5 -> Feb 6
- 3.0.3 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
- RC2 -> May 29 WTP will likely not participate in RC2, based on feedback from last year that RC2 came too soon, needed more fixing, less testing
- RC3 -> Jun 5
- RC4 -> Jun 12
- RC5 -> Jun 19
- GA -> Jun 24
- Project leads: please fix meta-data during July. 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
- In the works: Proposal to adjust bugzilla so bugzilla "products" match our subcomponents (currently have 4, need about 8?)
Teams Status and Focus for Coming Week
The minutes of the meetings are posted. Next meeting is next Monday same time. See details on the wiki page: WTP Performance Tests
- Ongoing triaging of incoming bug reports
- Working on updating bug backlogs
- Triaging remaining 3.0 requirements and targeted bugs
- Ongoing triage of incoming and existing bugs.
- Fixing and verifying bugs.
- JPT 2.0
- Working on:
- EclipseLink support
- Bugs for M7
- Working on:
- Feature exceptions
- Bug Fixes
- 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
- Build Declaration Process Refined - See WTP Build Process and Procedures
- 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.
- 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