Jump to: navigation, search

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

(3.2.4 Schedule)
(References)
 
(One intermediate revision by the same user not shown)
Line 96: Line 96:
 
== Other business  ==
 
== Other business  ==
  
* Google Summer of Code (GSoC)Program opportunities! Want to be a mentor?  Chance for some help with that pet project of yours!
+
* Time for spring cleaning. Project Leads, our Indigo IP Logs are due 5/18. So, it is a good time to ...
Check out the following sites: [http://wiki.eclipse.org/Google_Summer_of_Code Google Summer of Code] and [http://wiki.eclipse.org/Google_Summer_of_Code_2011_Ideas Current 2011 Ideas]
+
:: 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.  
  
* Discuss 2012 release train ("Juno") primarily targeting 4.2 release, 3.8 release also maintained, but secondary. 'Primary' means built and tested against 4.2 (with compatibility layer), and EPP packages use (only) the 4.2 workbench. We in WTP would still want to maintain one code stream, that is, not exploit new API only in 4.2, right? 3.8 would be tested/maintained as much as desired. See the [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05597.html Platform's position statement] for more of their perspective. Suggestions? Assumptions?
 
 
* Other ?
 
* Other ?
  
Line 108: Line 108:
 
Also, see  
 
Also, see  
  
Ongoing reminder: [http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08264.html Please test our M6 repositories]  
+
: [http://wiki.eclipse.org/Google_Summer_of_Code Google Summer of Code] and
 +
:: [http://wiki.eclipse.org/Google_Summer_of_Code_2011_Ideas Current 2011 Ideas]
  
Ongoing reminder: [http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08265.html Please check out JUnits running against Eclipse 4.1]
+
: [[WTP_3.3_Ramp_down_Plan_for_Indigo| 3.3 Rampdown plan]]  
  
[[WTP_3.3_Ramp_down_Plan_for_Indigo| 3.3 Rampdown plan]]  
+
: [http://www.eclipse.org/projects/project-plan.php?projectid=webtools Standard Format Plans]
  
[http://www.eclipse.org/projects/project-plan.php?projectid=webtools Standard Format Plans]
+
: [[WTP_3.2.x_Maintenance| WTP 3.2.x maintenance release plan]]
  
[[WTP_3.2.x_Maintenance| WTP 3.2.x maintenance release plan]]
+
: [[WTP_How_to:_Branching_Policy_and_Practices| how/when to branch code?]]  
  
[[WTP_How_to:_Branching_Policy_and_Practices| how/when to branch code?]]  
+
: [http://www.eclipse.org/projects/ip_log_selector.php IP Logs selector]
  
[http://www.eclipse.org/projects/ip_log_selector.php IP Logs selector]
+
: [[Team_thoughts_on_continuous_improvement_32| WTP Helios retrospective]].
  
[[Team_thoughts_on_continuous_improvement_32| WTP Helios retrospective]].
+
: See also the [[WTP Meeting Archive-Reference Page]].
 
+
 
+
See also the [[WTP Meeting Archive-Reference Page]].
+

Latest revision as of 12:08, 14 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

  • Last build before PMC review!
  • 3.2.4 build/ramp down and release dates.

3.2.4 Schedule

  • Propose change to next week's schedule:
Wednesday, Thursday to Smoke Test and Declare (instead of Thursday, Friday) due to long Easter weekend, for many.
3/11 M build
3/18 M build
3/25 M build
4/1 M build
4/8 M build
4/15 M build (after this build, begin PMC-review rampdown (+1 begins)) Anything following this would be only for serious regressions.
4/22 4/21 M build (after this build, begin +2)
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

Bug Review

Hotbugs [1]
Blocker and Critical
Bugs targeted to 3.2.4
Bugs targeted to (Dali) 2.3.4


WTP 3.3.0

  • Bug Review
Bugs targeted to 3.3 M7
Bugs targeted to (Dali) 3.0 M7
  • Several projects should re-tag soon (for M7) if not remove redundant null checks or dead code. See bug 340923. Discussion?

Schedule

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

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 ?

References

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