Skip to main content
Jump to: navigation, search

WTP 2009-08-13

WTP Development Status Meeting


Project Leads
Keith Y
Nitin Y
Chuck Y
Kaloyan Y
Raghu Y
Neil Y
David Y
Bob Y
Carl Y
Chris Y
Dave Y
Kate Y
Angel Y
Valentin Y
Gary Y
Nick Y
Gabriel Y
Rob Y
Ian Y
Aidyl Y

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

Announcements And Special Reports

  • It's New & Noteworthy time for M1.
  • Remember has some downtime scheduled for this weekend and next.
  • WTP 3.2 will be in June, 2010, as part of Helios
  • High level implications:
  • scratch use of "3.3"
  • use "helios" folder for standard plans, instead of "WTP 3.2"
  • Plans no longer due this week, but hopefully will see incremental progress soon.
  • xsl component complications (tbd, will have "source editing" call later, if needed)
Notes: will need to discuss more when concrete, but could investigate a minimal release
  • JBoss Studio and Module Dependencies?
Notes: Max will discuss details at JEE meetings, but sounds like as long as Module dependencies are finalized this year (M3? M4?) then JBoss can adapt.
Resolved to better mark tentative plans as tentative, in future. (Such as see

WTP Calendar

(Weekly Google Calendar updated through December)

For Galileo and Helios overall dates, see a Simultaneous Release Calendar

WTP 3.1.x

Current Build

Ready to declare latest build?


See also the Galileo ramp down dates

8/14 M Build
8/28 M Build (PMC Review starts following this build)
9/04 M Build Can this be our final build?
9/11 M Build Final Build
(9/25 Galileo SR1)
Galileo SR2 2/26/10 (will be WTP 3.1.2) (last Friday of February)


Targeted and fixed bugs for 3.1.1 or 2.2.1
Bugs still targeted to 3.1.0 or its release candidates

Galileo Maintenance Plan

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

WTP 3.2

  • Planning (initial plans due on or before first Milestone)
  • Planning (initial plans due on or before second Helios Milestone)
For general directions, you can use the 3.1 Project Plans reference.


M1 8/14
M2 9/25
Initial WTP 3.2 plans due 10/2 -- for Helios!
M3 11/05
M4 12/10

WTP 3.2 Plus Plus

  • We now have once-a-day Helios 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

  • cache coordination. See bug 284061 (Gary Karasiuk)
  • Our bugzilla workflow and arch. council's recommendations (David Carver's note to wtp-dev)
Note: carried over to subsequent week ... TODO: adopt, or come back to arch. council on why not


WTP 3.1 Post Mortem

ramp down plan and policies

See also the WTP Meeting Archive-Reference Page.

Back to the top