Jump to: navigation, search

Difference between revisions of "WTP 2011-01-13"

(1/13)
 
(3.2.3 schedule)
Line 143: Line 143:
 
===3.2.3 schedule===
 
===3.2.3 schedule===
  
::01/07 Declared M-build
 
 
::01/14 Declared M-build '''[contributed to Helios SR2 RC1 +2 due on 01/19]'''
 
::01/14 Declared M-build '''[contributed to Helios SR2 RC1 +2 due on 01/19]'''
 
:::PMC +1 review from 01/14 to 01/28
 
:::PMC +1 review from 01/14 to 01/28

Revision as of 16:08, 11 January 2011

WTP Development Status Meeting

Attendees

Project Leads
Carl
Angel
Keith
Nitin
Chuck
Kaloyan
Raghu
Neil
David
Committers
Bob
Konstantin
Chris
Dave
Larry
Kate
Tim
Valentin
Paul
Nick
Gabriel
Eric
Rob
Sam
Elson
Friends
Ian

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, 2011)


For Indigo/Helios overall dates, see a Simultaneous Release Calendar


WTP 3.2.3

  • Bug Review
Hotbugs [1]
Blocker and Critical
Bugs targeted to 3.2.3
Bugs targeted to 2.3.3

3.2.3 schedule

01/14 Declared M-build [contributed to Helios SR2 RC1 +2 due on 01/19]
PMC +1 review from 01/14 to 01/28
01/21 Declared M-build
01/28 Declared M-build [contributed to Helios SR2 RC2 +2 due on 02/02]
PMC +2 review from 01/28 to 02/04
02/04 Declared M-build [contributed to Helios SR2 RC3 +2 due on 02/09]
PMC +3 review from 02/04 to 02/11
02/11 Final M-build [contributed to Helios SR2 RC4 +2 due on 02/16]
02/25 Official Release


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

WTP 3.3.0

Planning

  • Standard Plans are done (right?)
  • Any anticipated IP requests that do not yet have a CQ Open? (Deadline is coming up ... M5?).

Schedule

8/13 WTP M1

9/24 WTP M2

11/4 WTP M3

12/10 WTP M4

Other business

  •  ?

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.x maintenance release plan

how/when to branch code?

WTP_3.2_Ramp_down_Plan_for_Helios

IP Logs selector

WTP Helios retrospective.


See also the WTP Meeting Archive-Reference Page.