WTP Development Status Meeting
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
(Weekly Google Calendar updated through June, 2011)
For Indigo/Helios overall dates, see a Simultaneous Release Calendar
Focus on Quality (Neil)
- Focus Item:
- Untargeted severity "Major" and higher bugs opened before June 1st, 2011 (This week - 27)
- Target to a specific release or "future" if planning to fix but not in the next release
- Adjust severity as appropriate
- Untargeted bugs and enhancements with patches attached over 1 year old (This week - 15; Last week - 15)
- Untargeted bugs and enhancements with patches attached (This week - 26; Last week - 26)
- Maintenance stream opened
- No I Build again this week to concentrate on Indigo release
- Proposed Smoketest procedure: Weekly smoketest required only for projects contributing week to week. Project lead's may request a WTP wide smoketest if submitting changes that may effect others. All projects will resume smoke testing after PMC-review starts until final build.
- 6/17 M build
- Regular weekly M builds
- 9/30 M build
- 10/7 M build (after this build, begin PMC-review ramp-down (+1 begins))
- 10/14 M build (after this build, begin +2)
- 10/21 M build (after this build, begin +3)
- 10/28 M build final build (with one week of buffer following this week, quiet week, until 11/4 (re-spin would require +3))
- 11/4 WTP 3.2.5 GA
See "references"  for detailed explanation of what these dates mean.
3.2.5 Bug Review
- rename RC4b to R and "quietly" put on downloads, to replicate [dw]
- update HTML to point to final versions of our prereq URLs [dw]
- update repository properties, b3aggrcon, etc. for final repository [dw]
- tag map files, soon. [dw]
- add docs to info center, that is, add info to bug 348355 [Neil] (Completed)
- new and noteworthy final, combined version? Do we do that? [Nitin]
- news item (for 6/22) [Nitin]
- RC4b build 06/07 (Quiet week begins) [Final build]
- GA 06/22
- Open bugs targeted to WTP 3.3 please triage!
- Release Review by EMO successful
Reminders for extra testing
- Use 4.1 as base, of our Indigo deliverables
- It's a good time to update tutorials, and in general all website content needs updating - Are you pointing to project overview? Is it up to date?, Highlighted new features in release?
- Coming to a city near you! - Try to attend Eclipse Indigo Demo Camps
- Should we, WTP, have more direct connection to Mylyn reporting ability?
- See bug 347261 - "Report Bug or Enhancements ... " is missing products
- ↑ 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 some "Simultaneous Release" due dates ... but it's hard to do much in that window, without disrupting everyone ... so we'll not use that buffer, except for the worst emergencies.]
- ↑ Hotbug Policy
- See also the WTP Meeting Archive-Reference Page.