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.
WTP 2010-03-11
Contents
WTP Development Status Meeting
Attendees
|
|
|
Note: feel free to correct any errors/omissions in above attendance record.
Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginning. Longer items or issues requiring discussion should go in the "Other business" section at end.
Announcements And Special Reports
- Congratulations to JAX-WS for successful move review. I assume we'll actually do move around 3/18?
WTP Calendar
(Weekly Google Calendar updated through June, 2010)
For Galileo and Helios overall dates, see a Simultaneous Release Calendar
Quality Focus Items (Neil)
- Focus Item:
- Untargeted bugs with patches attached opened before Jan 1st, 2010 (Current: 10, Last week: 16)
- Options:
- Mark invalid patches as obsolete
- Target bugs to a release or "future" if not a current release
- Old Bugs
WTP 3.2
- Ready to declare latest build?
- Bugs
Schedule
- M6 03/12 - API, UI Freeze. Accessibility Reports.
- M7 04/30
- RC1 05/14 (followed by weekly RCs, if needed)
- Final WTP 3.2 build 06/10
- (06/23 Helios Release)
Note: these (and our plan dates) are on 'Friday' of the week. But, we produce and test the build on Thursday of the week, and ideally declare on Thursday. The dates in the Google Web Tools group calendar are for 'Thursdays' since that's a calendar for committers. We give ourselves the buffer to Friday, as our "public" date, that others can pick up our build, just in case a regression is found on Thursday and we have to respin and retest. [Technically, some might say, we still have till the following Tuesday or Wednesday for "Simultaneous Release" due date ... but it's hard to do much in that window, without disrupting everyone ... so we'd not use that buffer, except for the worst emergencies.]
Other business
- Need to update Web Tools Platform Plans to include JSDT.
- Done ... but ... now webtools.jsdt plan link is broken?
- Need "policy and practice" on marking bugzilla items so they show up as "deffered". (Raghu)
- The recommended practice for marking plan items as deferred is to set the Target Milestone to 'Future' as in:
- keywords=plan&target_milestone=Future
- If sub-projects have different criteria, Project leads should adjust the query in the plan. Some of the sub-projects have used the following criteria:
- keywords=plan&target_milestone=-
- keywords=plan&target_milestone=4.0
- The recommended practice for marking plan items as deferred is to set the Target Milestone to 'Future' as in:
- We need to improve website content.
- we require some
quickchanges for JUnit V4
- Accessibility checklist required by end of M6 (at latest)
References
WTP_3.2_Ramp_down_Plan_for_Helios
See also the WTP Meeting Archive-Reference Page.