Difference between revisions of "WTP 2012-08-16"

From Eclipsepedia

Jump to: navigation, search
(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...)
 
(WTP Moving to GIT!)
 
(2 intermediate revisions by one user not shown)
Line 35: Line 35:
 
* Discuss process documents
 
* Discuss process documents
 
* Discuss Git configuration (best practices)
 
* Discuss Git configuration (best practices)
 +
** [http://wiki.eclipse.org/Platform-releng/Git_Workflows#Dealing_with_line_terminators discussion topic on line terminators]
 
* We should have a "sign off" build....
 
* We should have a "sign off" build....
 
* Discuss [http://wiki.eclipse.org/WTP_Git_Migration_Checklist Git Checklist]
 
* Discuss [http://wiki.eclipse.org/WTP_Git_Migration_Checklist Git Checklist]
* Start playing with Git now! [http://wiki.eclipse.org/Platform-releng/Git_Workflows This is very useful]
+
* Start playing with Git now! [http://wiki.eclipse.org/WTP_Git_Workflows WTP Git Workflows]
 
* [http://wiki.eclipse.org/WTP_Git_Migration_Home Git education wiki page]
 
* [http://wiki.eclipse.org/WTP_Git_Migration_Home Git education wiki page]
  
Line 67: Line 68:
  
 
* Build coming friday....  Release your changes!
 
* Build coming friday....  Release your changes!
 +
* EMF Validation, among others not in Kepler yet... may delay our inclusion in release train
 
* Start planning - top level document being created soon
 
* Start planning - top level document being created soon
  
Line 84: Line 86:
  
 
:[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_severity=blocker;bug_severity=critical;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;classification=WebTools  Blocker and Critical]
 
:[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_severity=blocker;bug_severity=critical;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;classification=WebTools  Blocker and Critical]
 
 
  
 
== Other business  ==
 
== Other business  ==

Latest revision as of 13:46, 16 August 2012

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

[edit] WTP Calendar

(Weekly Google Calendar updated through June, 2012)


For Juno overall dates, see the Simultaneous Release Calendar


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

[edit] WTP Moving to GIT!

[edit] WTP 3.4.1

  • Build coming friday.... Release your changes!

[edit] 3.4.1 Schedule

8/16 RC1 build (after this build, begin PMC-review ramp-down (+1 begins))
8/30 RC2 build (after this build, begin PMC-review ramp-down (+2 begins))
9/6 RC3 build (after this build, begin PMC-review ramp-down (+3 begins))
9/13 final M build (with one week of buffer following this week, quiet week, until 9/28 (re-spin would require +3))
9/28 Juno SR1 GA

[edit] Bug Review

Bugs targeted to 3.4.1
Hotbugs
Blocker and Critical

[edit] WTP 3.5.0 Kepler!

  • Build coming friday.... Release your changes!
  • EMF Validation, among others not in Kepler yet... may delay our inclusion in release train
  • Start planning - top level document being created soon

[edit] 3.5.0 Schedule

8/17 WTP M1 declare
8/24 Official Kepler 3.5.0 M1 availability - no declare


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

[edit] Bug Review

Bugs targeted to 3.5.0
Hotbugs [2]
Blocker and Critical

[edit] Other business

  • All project leads should update project metadata (bugzilla targets, release info, Kepler?)
  • Anything else?

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