Jump to: navigation, search

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

(WTP 3.3.0)
(Other business)
 
Line 92: Line 92:
 
:: please check your project's list of committers, and remove any "inactive" members, by May 4.  
 
:: please check your project's list of committers, and remove any "inactive" members, by May 4.  
 
:: please check if any contributor's are "on the verge" of becoming committers, and if so, that is, they should be committer for Indigo release, let's see if we can "get them in" before May 4.
 
:: please check if any contributor's are "on the verge" of becoming committers, and if so, that is, they should be committer for Indigo release, let's see if we can "get them in" before May 4.
 
  
  
 
* Other ?
 
* Other ?
 +
 +
*: Nitin asked about Babel maps ... and no one knew. Do they do something automatically? Or do we need to update something?
 +
:: Nitin will ask Babel project lead and send note to wtp-releng.
 +
:: Certainly any "new" maps (such as for Libra) would have to be added ... and doubt if "we" know how to do that for GIT repos.
  
 
== References  ==
 
== References  ==

Latest revision as of 14:25, 28 April 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

  •  ? - Any other announcements

WTP Calendar

(Weekly Google Calendar updated through June, 2011)


For Indigo/Helios overall dates, see a 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.4

  • PMC review will now be +3! (after we declare this week).
the expectation is only very serious bugs or regressions to be considered, as many teams plan to use this build as their main "final testing".

3.2.4 Schedule

4/29 M build (after this build, begin +3)
5/06 M build final build (with one week of buffer following this week, quiet week, until 5/12 (respin would requires +3))
5/13 WTP 3.2.4 GA

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

Bug Review

Hotbugs [2]
Blocker and Critical
Bugs targeted to 3.2.4
Bugs targeted to (Dali) 2.3.4
PMC Review/Approval Summary

WTP 3.3.0

  • Now in final build for M7 this week.
  • Reminder for common repo: do we need new repo for Libra contribution? Currently using
<repositories location="http://download.eclipse.org/libra/milestones/S-0.1.0M6-201103111139/repository/" description="Libra Contributions">
  • Reminder to test common repo:
http://download.eclipse.org/releases/staging/
  • Do we need a M7 New and Noteworthy?
It was decided we do not ... no "big UI" additions to brag about.

Schedule

M7 04/28 (for delivery to Indigo+2 on 05/03) (after this build, begin PMC +1)
RC1 05/12 (for delivery to Indigo+2 on 05/17) (after this build, still PMC +1)
RC2 05/19 (for delivery to Indigo+2 on 05/24) (after this build, begin PMC +2)
RC3 05/26 (for delivery to Indigo+2 on 05/31) (after this build, begin PMC +3)
RC4 06/02 (for delivery to Indigo+2 on 06/07) [Final build]
GA 06/22

Bug Review

Bugs targeted to 3.3 M7
Bugs targeted to (Dali) 3.0 M7
Unfixed bugs targeted to the past -- please triage!

Other business

  • Time for spring cleaning. Project Leads, our Indigo IP Logs are due 5/18. So, it is a good time to ...
please check your project's list of committers, and remove any "inactive" members, by May 4.
please check if any contributor's are "on the verge" of becoming committers, and if so, that is, they should be committer for Indigo release, let's see if we can "get them in" before May 4.


  • Other ?
  • Nitin asked about Babel maps ... and no one knew. Do they do something automatically? Or do we need to update something?
Nitin will ask Babel project lead and send note to wtp-releng.
Certainly any "new" maps (such as for Libra) would have to be added ... and doubt if "we" know how to do that for GIT repos.

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

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.