Skip to main content
Jump to: navigation, search

Difference between revisions of "WTP 2010-06-03"

(WTP 3.2)
(WTP 3.2)
(One intermediate revision by one other user not shown)
Line 122: Line 122:
* Ready to declare test [[WTP Smoke Test Results| latest build]]?
* Ready to declare test [[WTP Smoke Test Results| latest build]]?
* No Build to declare this week (Planning week)
* No Build to declare this week (Planning week)
* Propose RC4 be our final build. But hold off declaring it until Tuesday EOD. Comments? Questions? Objections?  
* Propose RC4 be our final build. But hold off declaring it until Tuesday EOD. Comments? Questions? Objections?  
* Bugs
* Bug Review
:[ Hotbugs] <ref>[[WTP/Hotbug_Policy| Hotbug Policy]]</ref>
:[ Hotbugs] <ref>[[WTP/Hotbug_Policy| Hotbug Policy]]</ref>
Line 138: Line 136:
:[ Plan items targeted to WTP 3.2]
:[ Plan items targeted to WTP 3.2]
:[ PMC Review Summary List]
:[ PMC Review Summary List]
Line 148: Line 145:
:RC4 06/03
:RC4 <del>06/03</del> 06/08
:<del>Final WTP 3.2 build 06/10</del>
:<del>Final WTP 3.2 build 06/10</del>
:(06/23 Helios Release)
:(06/23 Helios Release)

Latest revision as of 13:48, 3 June 2010

WTP Development Status Meeting


Project Leads

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 test latest build?
  • Propose RC4 be our final build. But hold off declaring it until Tuesday EOD. Comments? Questions? Objections?
  • Bug Review
Hotbugs [1]
Blocker and Critical
P1s that need attention
Plan items targeted to WTP 3.2
PMC Review Summary List


Remember we need to ramp down!

RC4 06/03 06/08
Final WTP 3.2 build 06/10
(06/23 Helios Release)

Date recently set/announced by EMO:

IP Logs due: Friday, May 28
Docuware due: Friday, May 28
Helios Review: Friday, June 11

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

Other business

  • WTP 3.2.0 Release Review: submitted.
Helios checklist
IP Log

  • Post WTP 3.2 release maintenance
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?
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
  • Migrate Incubator projects to Git - (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.


  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


Web Tools Platform Plans

IP Logs selector

WTP 3.1 Post Mortem

See also the WTP Meeting Archive-Reference Page.

Back to the top