WTP Development Status Meeting
Note: feel free to correct any errors/omissions in above attendance record.
Announcements And Special Reports
- Aug 1 - RC2
- All changes after Aug 1 require PMC approval (2 votes)
- Aug 8 - RC3 & final build
- Aug 15 - 3.0.1 GA
- Smoketest request to be issued, please complete smoketest by 3 PM Friday, at latest
Bug Lists for 3.0.1
- Blockers & Criticals (~8!)
- All 3.0.1 Hotbugs (~0)
- In tabular form:
- Current 3.0.1 & 2.0.1 targeted bugs (~16!)
- WOW! Congratulations!
- Web Tools
- Number Fixed for 3.0.1 (~236!)
- Java Server Faces
- Number Fixed for 3.0.1 (~2?)
- Dali JPA Tools
- Number Fixed for 2.0.1 (~30!)
- 301 PMC approval list
- 237141 - Chuck: patch available, performance problem, needed for 301
- David: Neil had some questions on this one, already fixed in older releases, so probably should go in here, fundamental issue is a performance hit, independent issue, will check in for next week
- 242648 - need to confirm with JBoss before approved, leave for next week for confirmation
- 194047 - Phil: 1 large file, probably not for 301
- 228366 - Nitin: will request for 301 PMC after review
- 231205 - Chuck: will provide more info for Nitin to review, hoping for 301 next week
- 233763 - Paul: dependant on the bug that Chuck's bug, assuming Chuck's bug is fixed, then no issues
- 235306 - Carl: v2 WTP, not v3
- 241550 - Phil: trying to figure out the affects of this are. Not a critical problem
- David: target to 302 or 31 if not a critical issue, if this is brought forward, then will probably need more explanation on this one, will update to major cuz doesn't sound like a critical problem
- 242587 - Brad: bug in JDT, platform 3.5, so should target to 3.1, no changes, close as a dup of the JDT bug
- 242628 - Phil: attach a patch for approval, will be submitted for PMC approval for 3.0.1
- Current 301 & 201 targeted bugs
- 150794 - Nitin: really want this into 3.0.1, will work on this one
- 204397 - Carl: copyright problem for 3.0, will update
- 211528 - Nitin: solved for 155, will bring forward, major problem for 3.0.1
- 223704 - Carl: may bump this out, will move out to 302
- 232502 - Carl: NLS support for TVT, will submit for 301 next week
- 241782 - Angel: will submit patch for rewview and PMC approval
- 242241 - Kathy: investigating right now, may or may not be submitting this for 301
- 242312 - Kathy: suspecting a straight forward fix, 301 early next week
- 242469 - Kathy: Junit fix, nothing shipped with Junit testing
Bi-weekly smoketest before we declare M1
- August 7th
- August 21st
- M1 declared on August 22nd (please complete the New and Noteworthy beforehand)
- David: Konstantin brought up moving up to 3.5 platform
- Konstantin: will need to pickup 3.5 platform, have checked in a couple of bugs that depends on new features in 3.5, should take advantage of them. Issue of backwards compatiblity, and is worth investigating. Architecture group to discuss.
- David: No hard dependencies on 3.5 for M1, until we have this discussion.
- Tim: Can have an architectural discussion on the benefits and actual cost and is it worth doing
- David: will update prereqs to 3.5 to smoketest against
- David: dates out here last week and haven't heard of any feedback, will pass to planning council
Two issues came up when discussing the planning process
- 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.
- 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.
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
- 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 final 3.0.1 submissions
- Deciding overall themes for 3.1
- 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