Jump to: navigation, search

Difference between revisions of "WTP 2010-07-01"

(WTP 3.2.1)
(WTP 3.3.0)
 
(8 intermediate revisions by the same user not shown)
Line 139: Line 139:
  
 
:[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.2.1&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.2.1]
 
:[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.2.1&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.2.1]
 +
 +
:[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=2.3.1&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 2.3.1]
  
 
=== Schedule ===
 
=== Schedule ===
Line 146: Line 148:
 
:::Project lead review and approval until July 1  
 
:::Project lead review and approval until July 1  
  
:7/1 Declared M-build RC1
+
:'''7/1 Declared M-build RC1 <== you are here'''
  
 
:::PMC +1 review: July 2 - July 8  
 
:::PMC +1 review: July 2 - July 8  
Line 170: Line 172:
 
Initial Planning during July? Final plans by end of September?  
 
Initial Planning during July? Final plans by end of September?  
  
Working assumption: objective is to work with both Platform 3.7 and 4.0?
+
Working assumption: objective is to work with both Platform 3.7 and 4.1?
 +
 
 +
See [http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg07684.html briefest Eclipse 4.0 intro]. One thing I forgot there, was a pointer to [https://dev.eclipse.org/mailman/listinfo/e4-dev e4-dev mailing list] ... that's were Eclipse 4.0 builds are currently discussed, announced (in addition to e4-only topics).
 +
 
 +
Eclipse 4.0 "comes with" following bundles from EMF:
 +
Does anyone know right off ... is this all we need (at runtime) from EMF?  
 +
 
 +
:org.eclipse.emf.common_2.6.0.v20100614-1136.jar
 +
:org.eclipse.emf.ecore.change_2.5.0.v20100521-1846.jar
 +
:org.eclipse.emf.ecore.xmi_2.5.0.v20100521-1846.jar
 +
:org.eclipse.emf.ecore_2.6.0.v20100614-1136.jar
 +
 
 +
Answer: we need at least emf.edit (if not others).
  
 
== Other business  ==
 
== Other business  ==
  
* ?
+
* We discussed bug for API addition: {{bug|120376}}
 +
: PMC would approve, but ... first choice should be to increment only service field (not minor field, as would sometimes be the case with "new API". Adopters can (still) specify a version range such as for example [1.3.4,2.0) to make sure they "get" the bundle with the right level of service for the new API.
 +
 
 +
* There was a request for ... and PLs reminded to ... create the "3.3" and "3.3 Mx" targets.
  
 
== References  ==
 
== References  ==

Latest revision as of 15:01, 1 July 2010

WTP Development Status Meeting

Attendees

Project Leads
Carl
Tim
Keith
Nitin
Chuck
Kaloyan
Raghu
Neil
David
Committers
Bob
Konstantin
Chris
Dave
Larry
Kate
Angel
Valentin
Paul
Nick
Gabriel
Eric
Rob
Sam
Friends
Elson
Ian
Aidyl

Note: feel free to correct any errors/omissions in above attendance record.

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 updated through June, 2010)


For Helios overall dates, see a Simultaneous Release Calendar


WTP 3.2.1


  • Bug Review
Hotbugs [1]
Blocker and Critical
P1s that need attention
PMC Approval Summary
Bugs targeted to 3.2.1
Bugs targeted to 2.3.1

Schedule

6/16 Map files branched, M (continuous) builds started
Project lead review and approval until July 1
7/1 Declared M-build RC1 <== you are here
PMC +1 review: July 2 - July 8
7/8 Declared M-build RC2
PMC +2 review: July 9 - July 15
7/15 Declared M-build RC3 <== final build, unless blockers found
PMC +3 review: July 16 - July 22
7/22 Declared M-build RC4 <== final build, if needed
July 23 - July 30 is "quiet week" to allow in depth testing with no changes
7/30 Official Release

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

WTP 3.3.0

Initial Planning during July? Final plans by end of September?

Working assumption: objective is to work with both Platform 3.7 and 4.1?

See briefest Eclipse 4.0 intro. One thing I forgot there, was a pointer to e4-dev mailing list ... that's were Eclipse 4.0 builds are currently discussed, announced (in addition to e4-only topics).

Eclipse 4.0 "comes with" following bundles from EMF: Does anyone know right off ... is this all we need (at runtime) from EMF?

org.eclipse.emf.common_2.6.0.v20100614-1136.jar
org.eclipse.emf.ecore.change_2.5.0.v20100521-1846.jar
org.eclipse.emf.ecore.xmi_2.5.0.v20100521-1846.jar
org.eclipse.emf.ecore_2.6.0.v20100614-1136.jar

Answer: we need at least emf.edit (if not others).

Other business

PMC would approve, but ... first choice should be to increment only service field (not minor field, as would sometimes be the case with "new API". Adopters can (still) specify a version range such as for example [1.3.4,2.0) to make sure they "get" the bundle with the right level of service for the new API.
  • There was a request for ... and PLs reminded to ... create the "3.3" and "3.3 Mx" targets.

References

  1. Hotbug Policy
  2. 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.]

Also, see

WTP 3.2.x maintenance release plan

how/when to branch code?

WTP_3.2_Ramp_down_Plan_for_Helios

Web Tools Platform Plans

IP Logs selector

WTP Helios retrospective.


See also the WTP Meeting Archive-Reference Page.