Jump to: navigation, search

Difference between revisions of "WTP 2009-11-19"

(WTP 3.2)
(Announcements And Special Reports)
Line 103: Line 103:
 
=== Announcements And Special Reports  ===
 
=== Announcements And Special Reports  ===
  
: build machine issues ... partially resolved. See bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=295394 295394]
+
* No status meeting next week.  
  
: It is time to submit proposals for [http://www.eclipsecon.org/2010/ EclipseCon 2010]. Deadline is December 18.  
+
* Build machine issues ... partially resolved. See bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=295394 295394]
  
:: This [http://oisinh.wordpress.com/2009/11/06/a-short-post-on-eclipsecon-2010/ blog entry by Program Chair] gives a good overview of what is expected for this year's EclipseCon.
+
* It is time to submit proposals for [http://www.eclipsecon.org/2010/ EclipseCon 2010]. Deadline is December 18.
 +
 
 +
:: This [http://oisinh.wordpress.com/2009/11/06/a-short-post-on-eclipsecon-2010/ blog entry by Program Chair] gives a good overview of what is expected and desired for this year's EclipseCon.
  
 
=== WTP Calendar  ===
 
=== WTP Calendar  ===

Revision as of 11:45, 19 November 2009

WTP Development Status Meeting

Attendees

Project Leads
Konstantin
Tim
Keith
Nitin
Chuck
Kaloyan
Raghu
Neil
David
Committers
Bob
Carl
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

  • No status meeting next week.
  • Build machine issues ... partially resolved. See bug 295394
  • It is time to submit proposals for EclipseCon 2010. Deadline is December 18.
This blog entry by Program Chair gives a good overview of what is expected and desired for this year's EclipseCon.

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:
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate
  • Ongoing Focus Items:
  • Mark invalid patches as obsolete
  • Target bugs to a release or "future" if not a current release

WTP 3.1.x

Declared builds to resume in January.


Schedule

See also the Galileo ramp down dates

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

  • Does anyone need a declared build next week?
  • Bugs
Hotbugs
Blocker and Critical
P1


Schedule

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

Other business

  • Plan to remove "contributors page". There's been no objections and no volunteers to maintain it.
Bug 295000 - Committers page is inaccurate and not maintained
  • Ok to remove unused performance bundles? See bug 295202.
Have heard from all but a few teams.
  • heads up for unit test changes to allow tests that depend on JUnit 4. Educate yourself, but no mass updates recommended at this time. See bug 153429.

References

WTP 3.1 Post Mortem

ramp down plan and policies

See also the WTP Meeting Archive-Reference Page.