Jump to: navigation, search

Difference between revisions of "WTP 2013-04-11"

(New page: == WTP Development Status Meeting == <small>Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginni...)
 
 
Line 75: Line 75:
 
**More tracking todo's
 
**More tracking todo's
 
**ideas?
 
**ideas?
 +
 +
*Start planning for CBI!  post Kepler
 +
** Form planning team - shared responsibilities - leveraging existing work done by CBI team
 +
** [[CBI| Eclipse Common Build Infrastructure home]]
  
 
*Google Summer of Code Ideas - http://wiki.eclipse.org/Google_Summer_of_Code_2013_Ideas
 
*Google Summer of Code Ideas - http://wiki.eclipse.org/Google_Summer_of_Code_2013_Ideas
Line 83: Line 87:
  
 
Also, see  
 
Also, see  
 
* [[CBI| Eclipse Common Build Infrastructure home]]
 
  
 
* [http://wiki.eclipse.org/WTP_Git_Workflows WTP Git Usage/Discussion page]
 
* [http://wiki.eclipse.org/WTP_Git_Workflows WTP Git Usage/Discussion page]

Latest revision as of 10:22, 11 April 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:
  • Triage:
  • 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


3.5.0 Schedule

04/11 Regular I build smoke / declare
04/18 Regular I build smoke / declare
04/25 Regular I build smoke / declare
M7 05/02 (for delivery to Kepler+2 on 05/07)(after this build, begin PMC +1)
RC1 05/16 (for delivery to Kepler+2 on 05/21)(after this build, still PMC +1)
RC2 05/23 (for delivery to Kepler+2 on 05/28)(after this build, begin PMC +2)
RC3 05/30 (for delivery to Kepler+2 on 06/04)(after this build, begin PMC +3)
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

  • Eclipsecon thoughts etc....
    • A few less attendees this year, but large numbers of new attendees!
    • Still amazed how many EMF related session there are.... :)
    • Justin did a great job at his VJET presentation Slides here
    • Neil also did a great job Slides here
    • Less Enterprise "Java" related topics this year... xtext / modeling / alm / mobile / javascript / orion
  • Thoughts on updating weekly status calls
    • Change time to earlier?
    • Highlight technical discussion... rotate responsibility
    • More tracking todo's
    • ideas?

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

Juno SR2 Simultaneous Release Schedule
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.