Jump to: navigation, search

Difference between revisions of "WTP 2011-08-04"

(WTP 3.4.0)
(3.4.0 Schedule)
 
Line 107: Line 107:
 
:...
 
:...
 
:8/12  M1 declare
 
:8/12  M1 declare
:8/19  Official WTP 3.4.0 M1 release - no declare
+
:8/19  Official WTP 3.4.0 M1 availability - no declare
 
:
 
:
 
:9/23  M2 declare
 
:9/23  M2 declare
:9/30  Official WTP 3.4.0 M2 release - no declare
+
:9/30  Official WTP 3.4.0 M2 availability - no declare
 
:
 
:
  
 
See "references" <ref>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.]</ref> for detailed explanation of what these dates mean.
 
See "references" <ref>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.]</ref> for detailed explanation of what these dates mean.
 
  
 
==== Bug Review ====
 
==== Bug Review ====

Latest revision as of 14:43, 4 August 2011

WTP Development Status Meeting

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

Vote has ended nominating Elson Yuen for Server Tools Project Lead, all positive votes, PMC and EMO(Mike M.) has also approved. Congratulations Elson!
eclipse.org infrastructure update on 7/30 - significant speed increase the downloads and builds. Carl: "3.2.5 Build time fallen from 24 hours to 5 hours".

WTP Calendar

(Weekly Google Calendar updated through June, 2011)


For Juno/Indigo overall dates, see the Simultaneous Release Calendar


Focus on Quality (Neil)

  • Focus Item:
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate

WTP 3.2.5

  • Projects should notify Chuck / Carl if it is known week to week they will not be participating, so smoke report template can be changed

3.2.5 Schedule

6/17 M build
...
Regular weekly M builds
...
9/30 M build
10/7 M build (after this build, begin PMC-review ramp-down (+1 begins))
10/14 M build (after this build, begin +2)
10/21 M build (after this build, begin +3)
10/28 M build final build (with one week of buffer following this week, quiet week, until 11/4 (re-spin would require +3))
11/4 WTP 3.2.5 GA

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

3.2.5 Bug Review

Bugs targeted to 3.2.5


WTP 3.3.1

3.3.1 (tentative) Schedule

7/14 M build
...
Regular weekly M builds
...
8/19 M build
8/26 M build (after this build, begin PMC-review ramp-down (+1 begins))
9/2 M build (after this build, begin +2)
9/9 M build (after this build, begin +3)
9/16 final M build (with one week of buffer following this week, quiet week, until 9/23 (re-spin would require +3))
9/23 SR1 GA

Bug Review

Bugs targeted to 3.3.1
Hotbugs [2]
Blocker and Critical
Open bugs targeted to WTP 3.3.0 good work triaging!
Open bugs targeted to the recent past

WTP 3.4.0

  • No declare this week - continuing to work through problems with version dependencies - Carl will report progress

3.4.0 Schedule

7/14 initial declare
...
Regular weekly I builds
...
8/12 M1 declare
8/19 Official WTP 3.4.0 M1 availability - no declare
9/23 M2 declare
9/30 Official WTP 3.4.0 M2 availability - no declare

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

Bug Review

Bugs targeted to 3.4.0
Hotbugs [4]
Blocker and Critical

Other business

Indigo release retrospective

References

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

Also, see

Google Summer of Code and
Current 2011 Ideas
3.3 Rampdown plan
Standard Format Plans
WTP 3.2.x maintenance release plan
how/when to branch code?
IP Logs selector
WTP Helios retrospective.
See also the WTP Meeting Archive-Reference Page.