Difference between revisions of "WTP 2013-06-06"

Revision as of 11:33, 6 June 2013

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

WTP Calendar

(Weekly Google Calendar)

For Juno/Kepler overall dates, see the Simultaneous Release Calendar

Focus on Quality (Neil)

• Improve:

• Major or higher severity bugs by project (This week - 134, last week - 131)

• Targeted to Future (candidates for severity downgrade?) (Total - 76, last week - 77)

• Triage:

• Untargeted bugs and enhancements with patches attached over 7 days old (This week - 63, Last week - 71)
• Untargeted severity "Major" and higher bugs opened over 7 days ago (This week - 49, Last week - 44)
• Options:

• Target to a specific release or "future" if planning to fix but not in the next release
• Adjust severity as appropriate

WTP 3.5: Kepler

• Smoke Test delayed slightly...
• Kepler release train
  • Ramp down plan for Kepler
  • PMC RC3 approved bugs
  • IP_log all set?
  • Our release bug
  • June 5/2013 - PMC-approved Review materials approved
  • Let's discuss New and Noteworthy....

3.5.0 Schedule

RC4 06/06 (for delivery to Kepler+2 on 06/11) [Final build]

06/26 Kepler GA

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

Bug Review

Bugs targeted to 3.5

Hotbugs ^[2]

Blocker and Critical

Other business - Long term tracking items

• Start planning for CBI! post Kepler
  • Form planning team - shared responsibilities - leveraging existing work done by CBI team
  • Eclipse Common Build Infrastructure home

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

• WTP Git Usage/Discussion page

• New Help for Old Friends

Juno SR2 Simultaneous Release Schedule

• Provisional API

Indigo release retrospective

Standard Format Plans

WTP 3.2.x maintenance release plan

how/when to branch code?

IP Logs selector

See also the WTP Meeting Archive-Reference Page.