WTP 2009-09-17

WTP Development Status Meeting

Attendees

Project Leads Konstantin Tim Keith Nitin Chuck an Raghu Neil David

Committers Bob Carl Chris Dave Naci Larry Kate Angel Valentin Paul Nick Gabriel Eric Kiril Cameron Karen Rob Sam

Friends Elson Ian Aidyl Simon

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports

• Congratulations for 3.1.1!

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 August 1st, 2009 (Previous Weeks: 54) (Current: 43)
• Options:

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

WTP 3.1.x

Schedule

See also the Galileo ramp down dates

SR1

(09/25 Galileo SR1) (WTP 3.1.1) (fourth Friday of September)

SR2

01/08 M Build

01/15 M Build for SR2 RC1

01/29 M Build for SR2 RC2 (PMC Review starts following this build)

02/05 M Build for SR2 RC3 Can this be our final build?

02/12 R Build Final Build

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

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?

• Planning (initial plans due on or before second Helios Milestone)

See http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg07100.html

For general directions, you can use the 3.1 Project Plans reference.

• Bugs

targeted to M2

Schedule

M2 9/25

Initial WTP 3.2 plans due 10/2 -- for Helios!

M3 11/06

M4 12/11

M5 01/29

M6 03/12

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.]

WTP 3.2G

• We have once-a-day Galileo-based WTP 3.2 builds. Same WTP code. Different pre-req Platform. The goal is to make sure our 3.2 stream is at least compatible with both Galileo and Helios. Or, if we can not literally achieve being compatible, we should document why not and at least understand it.

• Any issues?

Other business

•  ?

References

WTP 3.1 Post Mortem

ramp down plan and policies

See also the WTP Meeting Archive-Reference Page.