WTP 2010-06-10

From Eclipsepedia

Jump to: navigation, search

Contents

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
Eric X
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 Helios overall dates, see a Simultaneous Release Calendar



WTP 3.2

  • Ready to declare release!? Project Leads, please document your projects approval/status on our final vote page, by Monday 6/14, at the latest.


  • Bug Review
Hotbugs [1]
Blocker and Critical
P1s that need attention
Plan items targeted to WTP 3.2
PMC Review Summary List
3.2 targeted bugs Mark as fixed (if they were) or change target milestone.


Schedule

Remember we need to are past! ramp down

Signoff required by 6/14
Helios Review: Friday, June 11
Helios Release! 06/23
WTP 3.2.0 Release Review materials
Helios checklist
Overview
Detail
Approved, static IP Log


See "references" [2] for detailed explanation of what these dates mean.

Other business

  • Nitin reminds everyone to finish/send final N&N links/info
  • Carl reminds everyone to check "old help for new friends V" to see if anything needs to be added.
  • Next week's meeting (6/17) ... let's have our annual "debrief" meeting? See last year's notes. (Provide "input" to Planning council debrief meeting on 7/7).
  • I propose we still meet (briefly?) on 6/24, back to normal 7/1 (our first declared M build)
  • WTP 3.2 release maintenance
Started release plan document
Simultaneous Maintenance (Helios SR1, SR2) is a given (requirement)
Those are fourth Friday of September and February
Proposal for other off-cycle maintenance? WTP 3.2.1 end of July?
motivation:
given schedules of some adopter testing, it is anticipated several fixes for adopter scenarios will be desired during June.
Appears broad enough interest to propose WTP-wide maintenance (instead of specific sub-projects).
continue "controlled mode" for duration (since very short)
Project lead review and approval until July 1
PMC 1 review: July 2 - July 8
PMC 2 review: July 9 - July 15
PMC 3 review: July 16 - July 22
Release: July 30
Builds start approximately mid June
Weekly testing and declared builds during July
Our WTP repository would be updated, but not the common Helios repo or EPP packages (until SR1, WTP 3.2.2).
This is similar to what we did for WTP 3.0
Other?
  • Migrate Incubator projects to Git - http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01209.html (Dave Carver)
    • Estimated Time Frame: July after WTP 3.2 is out.
    • All active Incubator components/projects have agreed.
    • XML Security, XQuery, Vex, RelaxNG.
    • Allows for a lower risk area for Web Tools projects to get lessons learned for any other project migration.
    • Allows for updating any existing releng projects and processes to take advantage of git, or re-architect existing processes if necessary.
    • Allows for active feedback to eGit project on use of their plugin to help improve it for the entire eclipse community.

References

  1. Hotbug Policy
  2. 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.]

Also, see

WTP_3.2_Ramp_down_Plan_for_Helios

Web Tools Platform Plans

IP Logs selector

WTP 3.1 Post Mortem

See also the WTP Meeting Archive-Reference Page.