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

Latest revision as of 16:31, 16 March 2011

Contents

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.

WTP 3.2.4

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

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