Difference between revisions of "WTP 2010-06-17"

From Eclipsepedia

Jump to: navigation, search
(6/17)
 
(Attendees)
 
(11 intermediate revisions by one user not shown)
Line 75: Line 75:
 
|-
 
|-
 
| Eric  
 
| Eric  
| X
+
|  
 
|-
 
|-
 
| Rob
 
| Rob
Line 106: Line 106:
 
=== Announcements And Special Reports  ===
 
=== Announcements And Special Reports  ===
  
* WTP 3.2.0 is done! Congratulations!
+
 
 
* [http://www.eclipsecon.org/summiteurope2010/submissions/?page=submissions Eclipse Summit Europe (ESE) 2010]
 
* [http://www.eclipsecon.org/summiteurope2010/submissions/?page=submissions Eclipse Summit Europe (ESE) 2010]
 
* [http://www.eclipse.org/helios/heliosinaction.php Helios in Action (2 slots!)]
 
* [http://www.eclipse.org/helios/heliosinaction.php Helios in Action (2 slots!)]
 
  
 
=== WTP Calendar  ===
 
=== WTP Calendar  ===
Line 124: Line 123:
  
  
== WTP 3.2  ==
+
== WTP 3.2.0 ==
  
  
* Ready to <del>declare</del> release!? Project Leads, please document your projects approval/status on our [[WTP_R3.2.0_R320_06142010| final vote page]], by Monday 6/14, at the latest.
+
: WTP 3.2 is done! ... almost:
<!--
+
* No Build to declare this week (Planning week)
+
-->
+
  
 +
: Helios Release! 06/23
  
* Bug Review
+
: All
 +
:: check "old help for new friends V" to see if anything needs to be added.
 +
:: tag your released code with R3_2_0 (or R1_2_0 (JSDT), or R2_3_0 (Dali))
 +
::: makes later comparisons easier ... but, tagged map files are the final authority (vS20100615235519)
  
:[https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=WebTools&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&query_format=advanced&short_desc=hotbug%20hotbug_request&short_desc_type=anywordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&order=product%2Cchangeddate%20DESC%2Ctarget_milestone%2Cbug_severity%2Cpriority%2Cpriority%2Cbug_severity%2Cbug_severity%2Cassigned_to%2Cstatus_whiteboard%2Ctarget_milestone%2Ctarget_milestone%2Ccomponent%2Cvotes%20DESC%2Cbug_id Hotbugs] <ref>[[WTP/Hotbug_Policy| Hotbug Policy]]</ref>
+
: The releng team
 +
:: rename to "R" builds
 +
:: prep and finalize repository (http://download.eclipse.org/webtools/repository/helios/)
 +
:: prep for final downloads page (e.g. update prereq URLs)
  
:[https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=blocker&bug_severity=critical&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=WebTools&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&query_format=advanced&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&order=product%2Cchangeddate%20DESC%2Ctarget_milestone%2Cbug_severity%2Cpriority%2Cpriority%2Cbug_severity%2Cbug_severity%2Cassigned_to%2Cstatus_whiteboard%2Ctarget_milestone%2Ctarget_milestone%2Ccomponent%2Cvotes%20DESC%2Cbug_id&query_based_on= Blocker and Critical]
+
: Nitin?
 +
:: Final N&N polish/links?
 +
:: 3.2 Announcement?
  
:[https://bugs.eclipse.org/bugs/buglist.cgi?type1-0-0=notsubstring;field0-0-0=priority;columnlist=bug_status%2Cproduct%2Ccomponent%2Cassigned_to%2Creporter%2Cpriority%2Cbug_severity%2Cresolution%2Ctarget_milestone%2Cshort_desc;value2-0-0=3.0.5%20P%2C%201.5.5%20P%20;field2-0-0=target_milestone;classification=WebTools;type2-0-0=nowordssubstr;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;value1-0-0=3.1;type0-0-0=equals;value0-0-0=P1;field1-0-0=target_milestone;product=Dali%20JPA%20Tools;product=Java%20Server%20Faces;product=Web%20Tools;product=WTP%20Common%20Tools;product=WTP%20EJB%20Tools;product=WTP%20Java%20EE%20Tools;product=WTP%20Releng;product=WTP%20ServerTools;product=WTP%20Source%20Editing;product=WTP%20Webservices;product=WTP%20Website P1s that need attention]
+
== WTP 3.2.1 ==
  
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=&y_axis_field=product&z_axis_field=target_milestone&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=JSDT&product=Web+Tools&product=WTP+Common+Tools&product=WTP+Datatools&product=WTP+EJB+Tools&product=WTP+Java+EE+Tools&product=WTP+ServerTools&product=WTP+Source+Editing&product=WTP+Webservices&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=plan&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&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= Plan items targeted to WTP 3.2]
+
<!--
 +
* Ready to <del>declare</del> release!? Project Leads, please document your projects approval/status on our [[WTP_R3.2.0_R320_06142010| final vote page]], by Monday 6/14, at the latest.
  
:[http://www.eclipse.org/webtools/plans/3.2.0RC4/pmc-bug-approval.php PMC Review Summary List]
+
* No Build to declare this week (Planning week)
 +
-->
  
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=product&y_axis_field=target_milestone&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&target_milestone=2.3&target_milestone=2.3+M1&target_milestone=2.3+M2&target_milestone=2.3+M3&target_milestone=2.3+M4&target_milestone=2.3+M5&target_milestone=2.3+M6&target_milestone=2.3+M7&target_milestone=2.3+RC&target_milestone=2.3+RC1&target_milestone=2.3+RC2&target_milestone=2.3+RC3&target_milestone=2.3+RC4&target_milestone=2.3.0&target_milestone=2.3.0+M1&target_milestone=2.3.0+M2&target_milestone=2.3.0+M3&target_milestone=2.3.0+M4&target_milestone=2.3.0+M5&target_milestone=2.3.0+M6&target_milestone=2.3.0+RC0&target_milestone=2.3.0+RC1&target_milestone=2.3.0+RC2&target_milestone=2.3.0+RC3&target_milestone=2.3.0+RC4&target_milestone=3.2&target_milestone=3.2+M1&target_milestone=3.2+M2&target_milestone=3.2+M3&target_milestone=3.2+M4&target_milestone=3.2+M5&target_milestone=3.2+M6&target_milestone=3.2+M7&target_milestone=3.2+RC1&target_milestone=3.2+RC2&target_milestone=3.2+RC3&target_milestone=3.2+RC4&target_milestone=3.2+RC5&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&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= 3.2 targeted bugs] Mark as fixed (if they were) or change target milestone.
+
:[[WTP_3.2.x_Maintenance| WTP 3.2.x maintenance release plan]]
  
  
=== Schedule ===
+
: builds have been set up and are running
 +
:: recommend committers setup specific workspace for maintenance work, with final pde target runtime, etc.
 +
:: be sure to use appropriate branch of map files
 +
::: R3_2_maintenance (most)
 +
::: R1_2_maintenance (JSDT)
 +
::: R2_3_maintenance (Dali)
  
Remember we <del>need to</del> are past! [[WTP_3.2_Ramp_down_Plan_for_Helios| ramp down]]
+
: how/when to branch code?
  
: Signoff required by 6/14
+
In brief, while you are doing ONLY maintenance (so maintenance and "next major release"
: Helios Review: Friday, June 11
+
are exactly the same code) you can develop in only HEAD, but just be sure to release to the branched map files.
: Helios Release! 06/23
+
You can merge (or "compare") HEAD map files with branched map files, so they have the exact same version tags
 +
in both map files ... that is, there is no need to "release" twice (should have exact same version and qualifier in both builds,  
 +
if code is really exactly the same).
  
: WTP 3.2.0 Release Review materials
+
Remember to bump service field version ... normally +1, if destined for WTP 3.2.1, +100 only required if doing service for next major release, that will not be in a service release.
 +
 
 +
Once maintenance and "next major release" code streams start to differ, we have agreed, in the
 +
past, that code in the same map file, should all be branched together, at the same time, and comments in the map file updated.
 +
This makes it easier for others to "load up" an environment for what ever stream they are working on,
 +
where as if done bundle by bundle, no one can easily figure that out what's what.
  
:: [http://eclipse.org/helios/planning/SimultaneousReleaseOverview.php?action=project&projectid=webtools Helios checklist]
+
* Bug Review
:: [http://www.eclipse.org/webtools/releaseReviews/201006/WebTools3.2ReleaseOverview.pdf Overview]
+
:: [http://www.eclipse.org/webtools/releaseReviews/201006/WebTools3.2.pdf Detail]
+
:: [http://www.eclipse.org/webtools/releaseReviews/201006/Approved%20IP%20Log%20Webtools%209%20Consolidated%20-%20Helios.pdf Approved, static IP Log]
+
  
 +
:[https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=WebTools&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&query_format=advanced&short_desc=hotbug%20hotbug_request&short_desc_type=anywordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&order=product%2Cchangeddate%20DESC%2Ctarget_milestone%2Cbug_severity%2Cpriority%2Cpriority%2Cbug_severity%2Cbug_severity%2Cassigned_to%2Cstatus_whiteboard%2Ctarget_milestone%2Ctarget_milestone%2Ccomponent%2Cvotes%20DESC%2Cbug_id Hotbugs] <ref>[[WTP/Hotbug_Policy| Hotbug Policy]]</ref>
  
 +
:[https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=blocker&bug_severity=critical&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=WebTools&email1=&email2=&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&query_format=advanced&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&votes=&order=product%2Cchangeddate%20DESC%2Ctarget_milestone%2Cbug_severity%2Cpriority%2Cpriority%2Cbug_severity%2Cbug_severity%2Cassigned_to%2Cstatus_whiteboard%2Ctarget_milestone%2Ctarget_milestone%2Ccomponent%2Cvotes%20DESC%2Cbug_id&query_based_on= Blocker and Critical]
  
See "references" <ref>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.]</ref> for detailed explanation of what these dates mean.
+
:[https://bugs.eclipse.org/bugs/buglist.cgi?type1-0-0=notsubstring;field0-0-0=priority;columnlist=bug_status%2Cproduct%2Ccomponent%2Cassigned_to%2Creporter%2Cpriority%2Cbug_severity%2Cresolution%2Ctarget_milestone%2Cshort_desc;value2-0-0=3.0.5%20P%2C%201.5.5%20P%20;field2-0-0=target_milestone;classification=WebTools;type2-0-0=nowordssubstr;query_format=advanced;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;value1-0-0=3.1;type0-0-0=equals;value0-0-0=P1;field1-0-0=target_milestone;product=Dali%20JPA%20Tools;product=Java%20Server%20Faces;product=Web%20Tools;product=WTP%20Common%20Tools;product=WTP%20EJB%20Tools;product=WTP%20Java%20EE%20Tools;product=WTP%20Releng;product=WTP%20ServerTools;product=WTP%20Source%20Editing;product=WTP%20Webservices;product=WTP%20Website P1s that need attention]
  
== Other business  ==
 
  
* Nitin reminds everyone to finish/send final N&N links/info
 
  
* Carl reminds everyone to check "old help for new friends V" to see if anything needs to be added.
+
<!--
 +
=== Schedule ===
  
* Next week's meeting (6/17) ... let's have our annual "debrief" meeting? See [http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_31 last year's notes]. (Provide "input" to Planning council debrief meeting on 7/7).
 
  
* I propose we still meet (briefly?) on 6/24, back to normal 7/1 (our first declared M build)
 
  
* WTP 3.2 release maintenance
 
  
:: Started [[WTP_3.2.x_Maintenance| release plan document]]
 
  
:: Simultaneous Maintenance (Helios SR1, SR2) is a given (requirement)
 
::: Those are fourth Friday of September and February
 
  
:: Proposal for other off-cycle maintenance? WTP 3.2.1 end of July?
+
See "references" <ref>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.]</ref> for detailed explanation of what these dates mean.
 +
-->
  
::: motivation:
 
:::: given schedules of some adopter testing, it is anticipated several fixes for adopter scenarios will be desired during June.
 
:::: Appears broad enough interest to propose WTP-wide maintenance (instead of specific sub-projects).
 
  
::: continue "controlled mode" for duration (since very short)
+
== Helios Retrospective ==
  
:::: Project lead review and approval until July 1
+
For both our specific project, and the overall Helios release.
:::: PMC 1 review: July 2 - July 8
+
:::: PMC 2 review: July 9 - July 15
+
:::: PMC 3 review: July 16 - July 22
+
:::: Release: July 30
+
  
::: Builds start approximately mid June
+
Provide input to Planning council retrospective meeting on 7/7.
  
::: Weekly testing and declared builds during July
+
See [http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_31 last year's notes].
  
::: Our WTP repository would be updated, but not the common Helios repo or EPP packages (until SR1, WTP 3.2.2).  
+
and [http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_32 this year's page].
  
::: This is similar to what we did for WTP 3.0
+
== Other business  ==
  
::: Other?
 
  
* Migrate Incubator projects to Git - http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01209.html (Dave Carver)
+
* ?
** Estimated Time Frame: July after WTP 3.2 is out.
+
** All active Incubator components/projects have agreed.
+
** XML Security, XQuery, Vex, RelaxNG.
+
** Allows for a lower risk area for Web Tools projects to get lessons learned for any other project migration.
+
** Allows for updating any existing releng projects and processes to take advantage of git, or re-architect existing processes if necessary.
+
** Allows for active feedback to eGit project on use of their plugin to help improve it for the entire eclipse community.
+
  
 
== References  ==
 
== References  ==

Latest revision as of 12:49, 17 June 2010

Contents

[edit] WTP Development Status Meeting

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

[edit] Announcements And Special Reports

[edit] WTP Calendar

(Weekly Google Calendar updated through June, 2010)


For Helios overall dates, see a Simultaneous Release Calendar



[edit] WTP 3.2.0

WTP 3.2 is done! ... almost:
Helios Release! 06/23
All
check "old help for new friends V" to see if anything needs to be added.
tag your released code with R3_2_0 (or R1_2_0 (JSDT), or R2_3_0 (Dali))
makes later comparisons easier ... but, tagged map files are the final authority (vS20100615235519)
The releng team
rename to "R" builds
prep and finalize repository (http://download.eclipse.org/webtools/repository/helios/)
prep for final downloads page (e.g. update prereq URLs)
Nitin?
Final N&N polish/links?
3.2 Announcement?

[edit] WTP 3.2.1

WTP 3.2.x maintenance release plan


builds have been set up and are running
recommend committers setup specific workspace for maintenance work, with final pde target runtime, etc.
be sure to use appropriate branch of map files
R3_2_maintenance (most)
R1_2_maintenance (JSDT)
R2_3_maintenance (Dali)
how/when to branch code?

In brief, while you are doing ONLY maintenance (so maintenance and "next major release" are exactly the same code) you can develop in only HEAD, but just be sure to release to the branched map files. You can merge (or "compare") HEAD map files with branched map files, so they have the exact same version tags in both map files ... that is, there is no need to "release" twice (should have exact same version and qualifier in both builds, if code is really exactly the same).

Remember to bump service field version ... normally +1, if destined for WTP 3.2.1, +100 only required if doing service for next major release, that will not be in a service release.

Once maintenance and "next major release" code streams start to differ, we have agreed, in the past, that code in the same map file, should all be branched together, at the same time, and comments in the map file updated. This makes it easier for others to "load up" an environment for what ever stream they are working on, where as if done bundle by bundle, no one can easily figure that out what's what.

  • Bug Review
Hotbugs [1]
Blocker and Critical
P1s that need attention



[edit] Helios Retrospective

For both our specific project, and the overall Helios release.

Provide input to Planning council retrospective meeting on 7/7.

See last year's notes.

and this year's page.

[edit] Other business

  •  ?

[edit] References

  1. Hotbug Policy

Also, see

WTP_3.2_Ramp_down_Plan_for_Helios

Web Tools Platform Plans

IP Logs selector

WTP 3.1 Post Mortem

See also the WTP Meeting Archive-Reference Page.