WTP 2010-02-18

WTP Development Status Meeting

Attendees

Project Leads Carl Tim Keith Nitin Chuck Kaloyan Raghu Neil David

Committers Bob Konstantin Chris Dave Larry Kate Angel Valentin Paul Nick Gabriel Rob Sam

Friends Elson Ian Aidyl

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

•  ?

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: 16, Last week: 18)
• Options:

• Mark invalid patches as obsolete
• Target bugs to a release or "future" if not a current release

WTP 3.1.x

• Ready to declare WTP 3.1.2?!

Schedule

See also the Galileo ramp down dates

WTP 3.1.2 - Galileo SR2

(02/26 Galileo SR2) (WTP 3.1.2) (fourth Friday of February)

The time between 2/12 and 2/26 is meant for final adopter testing, web pages, update testing, etc.

Bugs

Major bugs targeted and unresolved for 3.1.2 or 2.2.2

P1 bugs targeted and unresolved for 3.1.2 or 2.2.2

All targeted and unresolved for 3.1.2 or 2.2.2

hotbugs

resolved for 3.1.2 or 2.2.2

Required PMC Review remains in effect.

Galileo Maintenance Plan

See WTP_3.1.x_Maintenance for documentation of scope of maintenance and approvals required.

WTP 3.2

• Ready to declare latest build?

• Bugs

Hotbugs

Blocker and Critical

P1s that need attention

Plan items targeted to WTP 3.2

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

• who knew you could combine IP Logs?

Each project is still responsible for their own ... but we'll report a "rolled up" version for release.

• We need to improve website and logo? See bug bug 301940 and bug bug 300475.

• we require some quick changes for JUnit V4

http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg07680.html

• Accessibility checklist required by end of M6 (at latest)

TODO: create a wiki "form" representing the above lists, for sub-projects to fill in.

References

WTP 3.1 Post Mortem

ramp down plan and policies

See also the WTP Meeting Archive-Reference Page.