Difference between revisions of "WTP 2011-03-17"

From Eclipsepedia

Jump to: navigation, search
(Other business)
 
(7 intermediate revisions by 2 users not shown)
Line 32: Line 32:
  
 
* Ready to declare [[WTP_Smoke_Test_Results| latest build]]?  
 
* Ready to declare [[WTP_Smoke_Test_Results| latest build]]?  
* Proposal for 3.2.4 build/ramp down and release dates - This proposal is from IBM, discussion to follow, if everyone is in agreement, we'll declare this the official schedule.
+
* Proposal for 3.2.4 build/ramp down and release dates - This proposal is the result from discussions with some committers and project leads. We'll discuss any objections, and if everyone is in agreement, we'll declare this the official schedule.
 
   
 
   
====3.2.4 Proposed Schedule
+
==== 3.2.4 Proposed Schedule ====
  
 
::3/11 M build
 
::3/11 M build
Line 68: Line 68:
  
 
* [[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://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08264.html Please test our M6 repositories]
 +
* [http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08265.html Please check out JUnits running against Eclipse 4.1]
 +
* M6 build declared, 3.3 stream open for business
 +
* No build this week (planning week for M7)
  
 
* Bug Review
 
* Bug Review
  
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&target_milestone=3.3%20M6&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs targeted to 3.3 M6]
+
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&target_milestone=3.3%20M7&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs targeted to 3.3 M7]
  
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&target_milestone=3.0%20M6&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs targeted to (Dali) 3.0 M6]
+
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=resolution&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&target_milestone=3.0%20M7&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs targeted to (Dali) 3.0 M7]
 
+
* [http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08264.html Please test our M6 repositories]
+
* [http://dev.eclipse.org/mhonarc/lists/wtp-releng/msg08265.html Please check out JUnits running against Eclipse 4.1]
+
  
 
=== Schedule ===
 
=== Schedule ===
  
: M6  03/10 (for delivery to Indigo+2 on 03/15)
 
 
: M7  04/28 (for delivery to Indigo+2 on 05/03)
 
: M7  04/28 (for delivery to Indigo+2 on 05/03)
 
: RC1 05/12 (for delivery to Indigo+2 on 05/17)
 
: RC1 05/12 (for delivery to Indigo+2 on 05/17)
Line 90: Line 90:
 
== Other business  ==
 
== Other business  ==
  
* Reminder that we (or, many of us?) will be moving to daylight saving time soon, on 3/13.  
+
* Reminder that we have (or, many of us have?) moved to daylight saving time, on 3/13.  
* Assuming/proposing there be no status meeting, in two weeks, 3/24, due to EclipseCon, but that we will still have declared builds as usual.  
+
* Assuming/proposing there be no status meeting next week, 3/24, due to EclipseCon, but that we will still have declared builds as usual.  
 
* Build releng changes:
 
* Build releng changes:
 
: - Changed wtp4x (Eclipse 4.1) builds to run only once per day (if changes to source code). Since, it is essentially a "test".   
 
: - Changed wtp4x (Eclipse 4.1) builds to run only once per day (if changes to source code). Since, it is essentially a "test".   
: - Hope to soon run unit tests with Eclipse 4.1 as well. Initial, local builds showed no new problems.  
+
: - Running unit tests also, with Eclipse 4.1.
: - turned off custom access rule handling in batch build {{bug|325066}}. This doubles number of access warnings, from 60K to 120K warnings. Either amount is unmanageable. Turning off saves a little time during build (20-30 minutes?). Feel free to discuss/dissent in {bug|325066}}.
+
: - turned off custom access rule handling in batch build {{bug|325066}}. This doubles number of access warnings, from 60K to 120K warnings. Either amount is unmanageable. Turning off saves a little time during build (20-30 minutes?). Feel free to discuss/dissent in {{bug|325066}}.
 +
: - In fact, these access warnings, apparently, add 50-80M to our log file, so I plan to remove them (that is, prevent them from being generated in the first place). Comments welcome in bug {{bug|339817}}.
 
: - added a "fast fail" check, if serious errors detected in log, such as a problem doing a cvs checkout, or similar. One problem is that if there are no serious errors, it results in a lot of red "<span style="color:#FF0000">Result: 1</span>" messages in build log notices. Will need to write our own ant task to overcome that (and other Ant limitations). Issues documented in {{bug|339166}}
 
: - added a "fast fail" check, if serious errors detected in log, such as a problem doing a cvs checkout, or similar. One problem is that if there are no serious errors, it results in a lot of red "<span style="color:#FF0000">Result: 1</span>" messages in build log notices. Will need to write our own ant task to overcome that (and other Ant limitations). Issues documented in {{bug|339166}}
*  1.2G cbi-wtp-wst.jsdt still shows up in "disk usage report" ... was a bug ever opened, for webmasters to remove that workspace from 'master'?
+
*  1.2G cbi-wtp-wst.jsdt still shows up in "disk usage report" ... fixed via {{bug|339749}}
 
* Other ?
 
* Other ?
  

Latest revision as of 16:31, 16 March 2011

Contents

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

[edit] Announcements And Special Reports

  •  ? - Any other announcements

[edit] WTP Calendar

(Weekly Google Calendar updated through June, 2011)


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


[edit] 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

[edit] WTP 3.2.4

  • Ready to declare latest build?
  • Proposal for 3.2.4 build/ramp down and release dates - This proposal is the result from discussions with some committers and project leads. We'll discuss any objections, and if everyone is in agreement, we'll declare this the official schedule.

[edit] 3.2.4 Proposed Schedule

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


[edit] WTP 3.3.0

  • Bug Review
Bugs targeted to 3.3 M7
Bugs targeted to (Dali) 3.0 M7

[edit] 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

[edit] Other business

  • Reminder that we have (or, many of us have?) moved to daylight saving time, on 3/13.
  • Assuming/proposing there be no status meeting next week, 3/24, due to EclipseCon, but that we will still have declared builds as usual.
  • Build releng changes:
- Changed wtp4x (Eclipse 4.1) builds to run only once per day (if changes to source code). Since, it is essentially a "test".
- Running unit tests also, with Eclipse 4.1.
- turned off custom access rule handling in batch build bug 325066. This doubles number of access warnings, from 60K to 120K warnings. Either amount is unmanageable. Turning off saves a little time during build (20-30 minutes?). Feel free to discuss/dissent in bug 325066.
- In fact, these access warnings, apparently, add 50-80M to our log file, so I plan to remove them (that is, prevent them from being generated in the first place). Comments welcome in bug bug 339817.
- added a "fast fail" check, if serious errors detected in log, such as a problem doing a cvs checkout, or similar. One problem is that if there are no serious errors, it results in a lot of red "Result: 1" messages in build log notices. Will need to write our own ant task to overcome that (and other Ant limitations). Issues documented in bug 339166
  • 1.2G cbi-wtp-wst.jsdt still shows up in "disk usage report" ... fixed via bug 339749
  • Other ?

[edit] References

  1. Hotbug Policy

Also, see

Standard Format Plans

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.