Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WTP 2008-06-12"

(Issues)
(Attendees)
 
(14 intermediate revisions by 3 users not shown)
Line 8: Line 8:
 
{| border="1"
 
{| border="1"
 
|+ Project Leads
 
|+ Project Leads
|width="80%"|Konstantin ||  
+
|width="80%"|Konstantin || Y
 
|-
 
|-
 
|Tim ||  
 
|Tim ||  
Line 14: Line 14:
 
|Nitin ||  
 
|Nitin ||  
 
|-
 
|-
|Kathy ||  
+
|Kathy || Y
 
|-
 
|-
|Chuck ||  
+
|Chuck || Y
 
|-
 
|-
 
|Naci ||  
 
|Naci ||  
 
|-
 
|-
|Raghu ||  
+
|Raghu || Y
 
|-
 
|-
 
|Neil ||  
 
|Neil ||  
 
|-
 
|-
|David ||
+
|David || Y
 
|-
 
|-
|Helen ||  
+
|Helen || Y
 
|-
 
|-
 
|Philippe ||  
 
|Philippe ||  
Line 35: Line 35:
 
|width="80%"|Bob ||  
 
|width="80%"|Bob ||  
 
|-
 
|-
|Carl ||  
+
|Carl || Y
 
|-
 
|-
|Dave ||  
+
|Dave || Y
 
|-
 
|-
|Phil ||  
+
|Phil || Y
 
|-
 
|-
|Kaloyan||  
+
|Kaloyan|| Y
 
|-
 
|-
 
|Larry||  
 
|Larry||  
 
|-
 
|-
|Amy||  
+
|Amy|| Y
 
|-
 
|-
|Kate||  
+
|Kate|| Y
 
|-
 
|-
|Angel||  
+
|Angel|| Y
 
|-
 
|-
|Brad||  
+
|Brad|| Y
 
|-
 
|-
 
|Valentin||  
 
|Valentin||  
Line 69: Line 69:
 
=== Announcements And Reports ===
 
=== Announcements And Reports ===
  
===Focus on Requirements Planning (David today ... and Raghu)===
+
===Focus on Requirements Planning (Raghu)===
  
Nearly Done. Two requests of Project Leads:
+
: Raghu: start talking about planning ... soon?
 
+
* Let's triage [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;component=core;component=Doc;component=Doc;component=Documentation;component=FAQ;component=Framework;component=General;component=General;component=J2EE%20Standard%20Tools;component=JSF%20Tools;component=jst.ejb;component=jst.j2ee;component=jst.jem;component=jst.jsp;component=jst.server;component=jst.servlet;component=jst.ws;component=releng;component=UI;component=Web%20Standard%20Tools;component=wst.command;component=wst.common;component=wst.css;component=wst.dtd;component=wst.html;component=wst.internet;component=wst.javascript;component=wst.jsdt;component=wst.rdb;component=wst.server;component=wst.sse;component=wst.validation;component=wst.web;component=wst.ws;component=wst.wsdl;component=wst.wsi;component=wst.xml;component=wst.xsd;component=Web%20Standard%20Tools;component=Website;component=core;component=jst.ejb;component=jst.j2ee;component=jst.jem;component=jst.jsp;component=jst.server;component=jst.servlet;component=jst.ws;component=releng;component=wst.command;component=wst.common;component=wst.css;component=wst.dtd;component=wst.html;component=wst.internet;component=wst.javascript;component=wst.jsdt;component=wst.rdb;component=wst.server;component=wst.sse;component=wst.validation;component=wst.web;component=wst.ws;component=wst.wsdl;component=wst.wsi;component=wst.xml;component=wst.xsd;email1=;email2=;emailtype1=substring;emailtype2=substring;field-1-0-0=classification;field-1-1-0=product;field-1-2-0=component;field-1-3-0=bug_status;field-1-4-0=keywords;field0-0-0=target_milestone;keywords=plan;keywords_type=allwords;long_desc=;long_desc_type=allwordssubstr;product=Dali%20JPA%20Tools;product=Java%20Server%20Faces;product=Web%20Tools;query_format=advanced;remaction=;short_desc=;short_desc_type=allwordssubstr;status_whiteboard=;status_whiteboard_type=allwordssubstr;type-1-0-0=anyexact;type-1-1-0=anyexact;type-1-2-0=anyexact;type-1-3-0=anyexact;type-1-4-0=allwords;type0-0-0=nowordssubstr;value-1-0-0=WebTools;value-1-1-0=Dali%20JPA%20Tools%2CJava%20Server%20Faces%2CWeb%20Tools;value-1-2-0=core%2CDoc%2CDoc%2CDocumentation%2CFAQ%2CFramework%2CGeneral%2CGeneral%2CJ2EE%20Standard%20Tools%2CJSF%20Tools%2Cjst.ejb%2Cjst.j2ee%2Cjst.jem%2Cjst.jsp%2Cjst.server%2Cjst.servlet%2Cjst.ws%2Creleng%2CUI%2CWeb%20Standard%20Tools%2Cwst.command%2Cwst.common%2Cwst.css%2Cwst.dtd%2Cwst.html%2Cwst.internet%2Cwst.javascript%2Cwst.jsdt%2Cwst.rdb%2Cwst.server%2Cwst.sse%2Cwst.validation%2Cwst.web%2Cwst.ws%2Cwst.wsdl%2Cwst.wsi%2Cwst.xml%2Cwst.xsd%2CWeb%20Standard%20Tools%2CWebsite%2Ccore%2Cjst.ejb%2Cjst.j2ee%2Cjst.jem%2Cjst.jsp%2Cjst.server%2Cjst.servlet%2Cjst.ws%2Creleng%2Cwst.command%2Cwst.common%2Cwst.css%2Cwst.dtd%2Cwst.html%2Cwst.internet%2Cwst.javascript%2Cwst.jsdt%2Cwst.rdb%2Cwst.server%2Cwst.sse%2Cwst.validation%2Cwst.web%2Cwst.ws%2Cwst.wsdl%2Cwst.wsi%2Cwst.xml%2Cwst.xsd;value-1-3-0=NEW%2CASSIGNED%2CREOPENED;value-1-4-0=plan;value0-0-0=Future%2C%204.0%2C%203.0.1;votes=;query_based_on= remaining list of 'plan' keyword items] that are not resolved, and not marked future or not targeted. (i.e. it doesn't make sense to have marked 'plan' but untargeted ... or, what does it mean?)
+
 
+
* Let's triage [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=enhancement&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=WebTools&component=core&component=Doc&component=Doc&component=Documentation&component=FAQ&component=Framework&component=General&component=General&component=J2EE%20Standard%20Tools&component=JSF%20Tools&component=jst.ejb&component=jst.j2ee&component=jst.jem&component=jst.jsp&component=jst.server&component=jst.servlet&component=jst.ws&component=releng&component=UI&component=Web%20Standard%20Tools&component=wst.command&component=wst.common&component=wst.css&component=wst.dtd&component=wst.html&component=wst.internet&component=wst.javascript&component=wst.jsdt&component=wst.rdb&component=wst.server&component=wst.sse&component=wst.validation&component=wst.web&component=wst.ws&component=wst.wsdl&component=wst.wsi&component=wst.xml&component=wst.xsd&component=Web%20Standard%20Tools&component=Website&component=core&component=jst.ejb&component=jst.j2ee&component=jst.jem&component=jst.jsp&component=jst.server&component=jst.servlet&component=jst.ws&component=releng&component=wst.command&component=wst.common&component=wst.css&component=wst.dtd&component=wst.html&component=wst.internet&component=wst.javascript&component=wst.jsdt&component=wst.rdb&component=wst.server&component=wst.sse&component=wst.validation&component=wst.web&component=wst.ws&component=wst.wsdl&component=wst.wsi&component=wst.xml&component=wst.xsd&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=target_milestone&field-1-4-0=bug_status&field-1-5-0=bug_severity&field-1-6-0=keywords&field0-0-0=target_milestone&keywords=helpwanted&keywords_type=nowords&long_desc=&long_desc_type=allwordssubstr&product=Dali%20JPA%20Tools&product=Java%20Server%20Faces&product=Web%20Tools&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&target_milestone=2.0%20RC0&target_milestone=2.0&target_milestone=3.0&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=anyexact&type-1-5-0=anyexact&type-1-6-0=nowords&type0-0-0=nowordssubstr&value-1-0-0=WebTools&value-1-1-0=Dali%20JPA%20Tools%2CJava%20Server%20Faces%2CWeb%20Tools&value-1-2-0=core%2CDoc%2CDoc%2CDocumentation%2CFAQ%2CFramework%2CGeneral%2CGeneral%2CJ2EE%20Standard%20Tools%2CJSF%20Tools%2Cjst.ejb%2Cjst.j2ee%2Cjst.jem%2Cjst.jsp%2Cjst.server%2Cjst.servlet%2Cjst.ws%2Creleng%2CUI%2CWeb%20Standard%20Tools%2Cwst.command%2Cwst.common%2Cwst.css%2Cwst.dtd%2Cwst.html%2Cwst.internet%2Cwst.javascript%2Cwst.jsdt%2Cwst.rdb%2Cwst.server%2Cwst.sse%2Cwst.validation%2Cwst.web%2Cwst.ws%2Cwst.wsdl%2Cwst.wsi%2Cwst.xml%2Cwst.xsd%2CWeb%20Standard%20Tools%2CWebsite%2Ccore%2Cjst.ejb%2Cjst.j2ee%2Cjst.jem%2Cjst.jsp%2Cjst.server%2Cjst.servlet%2Cjst.ws%2Creleng%2Cwst.command%2Cwst.common%2Cwst.css%2Cwst.dtd%2Cwst.html%2Cwst.internet%2Cwst.javascript%2Cwst.jsdt%2Cwst.rdb%2Cwst.server%2Cwst.sse%2Cwst.validation%2Cwst.web%2Cwst.ws%2Cwst.wsdl%2Cwst.wsi%2Cwst.xml%2Cwst.xsd&value-1-3-0=2.0%20RC0%2C2.0%2C3.0&value-1-4-0=NEW%2CASSIGNED%2CREOPENED&value-1-5-0=enhancement&value-1-6-0=helpwanted&value0-0-0=Future%2C%204.0%2C%203.0.1&votes=&order=map_components.name%2Cmap_components.name%2Cbugs.delta_ts%2Cbugs.creation_ts%2Cbugs.status_whiteboard%2Cbugs.status_whiteboard%2Cmap_components.name%2Cbugs.status_whiteboard%2Cbugs.bug_id&query_based_on=  remaining list of 'enhancements' with a 3.0 target].
+
 
+
* Project leads, please take 20 minutes to polish [[Web_Tools_Platform_Release_3.0_Requirements]]
+
** If anything is in "proposed", move to committed or deferred
+
** Make sure any "completed" item is categorized as one of the themes, or "other" (just to show it does fit any of the standard ones).
+
 
+
*Minutes:
+
: Raghu: start talking about planning in the next mtg
+
  
 
== Post WTP 2.0.2 ==
 
== Post WTP 2.0.2 ==
Line 93: Line 82:
  
 
*Minutes:
 
*Minutes:
:Carl: working with JBoss to get the patch refined
+
:Carl: adding 233196, working on it
:235306: possible other patch, usage error
+
:235306: working with users on this
:Konstantin: 234404, 235893 opened for 202 release
+
:204153: no longer requested as a patch for the 202 stream
:204153, note sent to Nitin for update
+
:David: will get started on this next week
  
 
== WTP 3.0 End-Game ==
 
== WTP 3.0 End-Game ==
Line 107: Line 96:
  
 
*[http://wiki.eclipse.org/WTP_Functional_Test_R30_RC Overall Release Candidate Test Plan & Results]
 
*[http://wiki.eclipse.org/WTP_Functional_Test_R30_RC Overall Release Candidate Test Plan & Results]
 +
 +
*The [http://www.eclipse.org/webtools/releases/3.0.0/ 3.0 Release] pages should be reviewed by everyone to ensure accuracy.  Information or screenshots in the New and Noteworthy may need updating, and there is a page for Release Notes.  Good candidates for release notes include major fixes that were deferred to 3.0.1.
 +
  
 
=== Schedule ===
 
=== Schedule ===
Line 141: Line 133:
 
=== Bug Lists to Ramp Down ===
 
=== Bug Lists to Ramp Down ===
  
:[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=%7C%2C%2C All Blockers and Criticals] (~11) (~(15)
+
:[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=%7C%2C%2C All Blockers and Criticals] (~14)
  
 
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=hot+bug&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&target_milestone=3.0+RC1&target_milestone=3.0+RC2&target_milestone=3.0+RC3&target_milestone=3.0+RC4&target_milestone=3.0+RC5&target_milestone=2.0+RC1&target_milestone=2.0+RC2&target_milestone=2.0+RC3&target_milestone=2.0+RC4&target_milestone=2.0+RC5&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&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= All Hot Bugs and Requests] (~0)
 
:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=hot+bug&classification=WebTools&product=Dali+JPA+Tools&product=Java+Server+Faces&product=Web+Tools&target_milestone=3.0+RC1&target_milestone=3.0+RC2&target_milestone=3.0+RC3&target_milestone=3.0+RC4&target_milestone=3.0+RC5&target_milestone=2.0+RC1&target_milestone=2.0+RC2&target_milestone=2.0+RC3&target_milestone=2.0+RC4&target_milestone=2.0+RC5&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&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= All Hot Bugs and Requests] (~0)
Line 157: Line 149:
 
*Minutes:
 
*Minutes:
  
=== Thursday to Tuesday HEAD Builds? ===  
+
== WTP 3.0.1 ==
  
See [http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg06109.html Proposal] to keep HEAD very clean, so it's essentially an I-build without 'release'.
+
No specific plan yet, but some teams have started doing 3.0.1 work, so be sure to follow guidelines:
  
Do they need to be automated? 6 hours? 8 hours? Or, is "on demand" easy enough?
+
:;*[[WTP How to: Branching Policy and Practices]]
 
+
:::In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.  
== Release Review Requirements ==
+
:::The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
 
+
* Need zip file of about.html files by 5/15
+
* [http://www.eclipse.org/projects/whatsnew.php Release Review] will be June 4th, 11 AM Eastern Time. All (sub) project leads are encouraged to phone in.
+
*Minutes:
+
:David: We passed!  Good job!
+
 
+
==== IP Log ====
+
 
+
* In general, Project leads should review our [http://www.eclipse.org/webtools/iprelated/ip_log.php IP Log] for completeness and correctness.
+
 
+
* non-Committer Contributions
+
:: * bugzillas with contributed patches should be marked with '''contributed''' keyword
+
:: * There are some [http://www.eclipse.org/webtools/phpqueries/wtp-ip-tools.php WTP IP Tools] to help explore potential contributions.
+
 
+
==== Copyrights ====
+
 
+
* Make sure copyrights are up-to-date and according to Eclipse Foundation form:
+
::See [http://www.eclipse.org/legal/copyrightandlicensenotice.php Default Eclipse Foundation Copyright and License Notice]
+
 
+
==== Check for "license files" ====
+
 
+
* Check 'about.html' files exists
+
* are valid
+
* have correct "layout" in directories
+
* References:
+
 
+
::In the general eclipse legal section<br />
+
::http://www.eclipse.org/legal/
+
 
+
::Is one page that speaks to the about files directly
+
::http://www.eclipse.org/legal/epl/about.php
+
 
+
::In particular, note there are two that refer to literal HTML only versions, to use as your starting point.<br />
+
::http://www.eclipse.org/legal/epl/about.html<br />
+
::http://www.eclipse.org/legal/epl/longabout.html
+
 
+
::Also, please read <br />
+
::http://www.eclipse.org/legal/guidetolegaldoc.php#Abouts <br />
+
::It goes into detail about the locations, needs for plugins and features, and also mentions that third party content requires a seperate license file.
+
 
+
*Minutes
+
:David: about.html files, maybe asking for some help in the about.html files
+
  
 
== Performance Focus (Kaloyan) ==
 
== Performance Focus (Kaloyan) ==
Line 250: Line 200:
 
==== releng ====  
 
==== releng ====  
  
* We will be changing the way we generate source features/plugins
+
* tweaks to downloads page, 202 patch builds, prepare 301 maintenance builds, better integrate Incubation Builds, integrate production of update site via cruise control tasks.
:: See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132094 bug 132094] for details, implications, and links to more info.
+
 
+
:* Work on features is coming up: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=221449 bug 221449]
+
  
 
== References ==
 
== References ==
Line 259: Line 206:
 
:;*[[WTP Performance Tests]]
 
:;*[[WTP Performance Tests]]
 
:;*[[WTP:_Tweaking_Access_Rules | Tweaking the Access Rules for WTP]]
 
:;*[[WTP:_Tweaking_Access_Rules | Tweaking the Access Rules for WTP]]
:*Branching Strategy
+
:;*[[WTP How to: Branching Policy and Practices]]
::*Please review and comment on the [[WTP How to: Branching Policy and Practices]] guide.
+
:::In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
:::In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well.  We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.
+
:::The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
 
:*Instructions for tagging existing and new WTP wiki pages can be found at [[:Category:Eclipse Web Tools Platform Project | WTP's Category page]]; remember, we can create subcategories as well
 
:*Instructions for tagging existing and new WTP wiki pages can be found at [[:Category:Eclipse Web Tools Platform Project | WTP's Category page]]; remember, we can create subcategories as well
 
:*This Week's Smoke Test Results
 
:*This Week's Smoke Test Results
Line 277: Line 224:
 
::[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&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= Current WTP Bug Day bugs] (~53)
 
::[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&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= Current WTP Bug Day bugs] (~53)
  
 +
=== Release Review Requirements References ===
 +
 +
==== IP Log ====
 +
 +
* In general, Project leads should review our [http://www.eclipse.org/webtools/iprelated/ip_log.php IP Log] for completeness and correctness.
 +
 +
* non-Committer Contributions
 +
:: * bugzillas with contributed patches should be marked with '''contributed''' keyword
 +
:: * There are some [http://www.eclipse.org/webtools/phpqueries/wtp-ip-tools.php WTP IP Tools] to help explore potential contributions.
 +
 +
==== Copyrights ====
 +
 +
* Make sure copyrights are up-to-date and according to Eclipse Foundation form:
 +
::See [http://www.eclipse.org/legal/copyrightandlicensenotice.php Default Eclipse Foundation Copyright and License Notice]
 +
 +
==== Check for "license files" ====
 +
 +
* Check 'about.html' files exists
 +
* are valid
 +
* have correct "layout" in directories
 +
* References:
 +
 +
::In the general eclipse legal section<br />
 +
::http://www.eclipse.org/legal/
 +
 +
::Is one page that speaks to the about files directly
 +
::http://www.eclipse.org/legal/epl/about.php
 +
 +
::In particular, note there are two that refer to literal HTML only versions, to use as your starting point.<br />
 +
::http://www.eclipse.org/legal/epl/about.html<br />
 +
::http://www.eclipse.org/legal/epl/longabout.html
 +
 +
::Also, please read <br />
 +
::http://www.eclipse.org/legal/guidetolegaldoc.php#Abouts <br />
 +
::It goes into detail about the locations, needs for plugins and features, and also mentions that third party content requires a seperate license file.
  
 
== Bug Backlogs ==
 
== Bug Backlogs ==

Latest revision as of 14:30, 18 June 2008

WTP Development Status Meeting 2008-05-29

Attendees

Project Leads
Konstantin Y
Tim
Nitin
Kathy Y
Chuck Y
Naci
Raghu Y
Neil
David Y
Helen Y
Philippe
Committers
Bob
Carl Y
Dave Y
Phil Y
Kaloyan Y
Larry
Amy Y
Kate Y
Angel Y
Brad Y
Valentin
Gary
Friends
Nick
Gilbert

Announcements And Reports

Focus on Requirements Planning (Raghu)

Raghu: start talking about planning ... soon?

Post WTP 2.0.2

  • Some issues are still being investigated.
  • 201318 [hotbug] EAR Libraries container fails to initialize for 2...
  • 230256 [hotbug_request] jst.jee JEEDeployableFactory refuses to load ejb3 module
  • 235893 [hotbug] web.xml is corrupted when using add new Servlet wizard
  • 204153 [hotbug] Assert statement failed - expecting thread to be null
  • Minutes:
Carl: adding 233196, working on it
235306: working with users on this
204153: no longer requested as a patch for the 202 stream
David: will get started on this next week

WTP 3.0 End-Game

Are we done? Anyone investigating a potential stop ship bug?

  • The 3.0 Release pages should be reviewed by everyone to ensure accuracy. Information or screenshots in the New and Noteworthy may need updating, and there is a page for Release Notes. Good candidates for release notes include major fixes that were deferred to 3.0.1.


Schedule

Ganymede 06/17
Code done by Wed. 6/11
Smoke tests on Thur. 6/12
"Unofficial Declare" on Friday 6/13
Make official on Tuesday 6/17

Builds

  • Currently running
  • Mintues:

Testing

  • Minutes:
Teams need to update the test results

Issues

This bug/issue is not marked fixed ... are we doing anything here?
The help has a file called "Limitations and Known Issues" - this functions as a type of readme so that users can easily search for problems that have known workarounds.

This will be kept in the help, team leads pls review current content and add anything extra

Kate has opened a bug 233531, please use to add updates using comments

Bug Lists to Ramp Down

All Blockers and Criticals (~14)
All Hot Bugs and Requests (~0)
All Remaining Targeted Enhancements (~1)
3.0 RC Blockers/Criticals (~10)
Remaining Targeted Bugs (~45)
Note: a 3.0.1 target was added to bugzilla (not M301 301), to better re-target some of the bugs.
Resolved but Unverified Blockers/Criticals By Assignee (~42)
  • Minutes:

WTP 3.0.1

No specific plan yet, but some teams have started doing 3.0.1 work, so be sure to follow guidelines:

In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.

Performance Focus (Kaloyan)

No progress for the last two weeks. Still fighting with the Results Graph Generator.

  • Minutes
Kaloyan: a collegue is getting familiar with this, no progress so far

API Tools/Scans (Kaloyan)

Can we run reports? Though they are hard to spot errors since out of date ... perhaps we can "diff" reports?

Other business

BobF: meta-data: happy to round up the webpage?
David: some projects do not point to a pheonix style page
Action: by July: sub-project to get rid of or update pages to be consistent with pheonix style page

Teams Status and Focus for Coming Week

Source Editing

  • Ongoing triaging of incoming bug reports
  • Working on updating bug backlogs
  • Triaging remaining 3.0 requirements and targeted bugs

Server Tools

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing and verifying bugs.

Java EE

Dali JPT

  • JPT 2.0
    • Working on:
      • EclipseLink support
      • Bugs for M7
      • Performance

JSF

  • Feature exceptions
  • Bug Fixes

releng

  • tweaks to downloads page, 202 patch builds, prepare 301 maintenance builds, better integrate Incubation Builds, integrate production of update site via cruise control tasks.

References

In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
  • Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well
  • This Week's Smoke Test Results
WTP Smoke Test Results R30
Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
PMC Candidate Review Request Checklist - See the updated PMC Review document with attention to the "How To Prepare a PMC Defect Candidate" section
Adopter Migration Information for WTP 2.0 - Please add any details for your component.
  • Website
Documentation on Setting up your system for Web Tools Web site development and Using Web Tools Phoenix PHP templates is on the wiki at Web Tools Web Site Development.
  • Bug Day
Monitor and participate in Bug Day if you would like.
Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in IRC
Current WTP Bug Day bugs (~53)

Release Review Requirements References

IP Log

  • In general, Project leads should review our IP Log for completeness and correctness.
  • non-Committer Contributions
* bugzillas with contributed patches should be marked with contributed keyword
* There are some WTP IP Tools to help explore potential contributions.

Copyrights

  • Make sure copyrights are up-to-date and according to Eclipse Foundation form:
See Default Eclipse Foundation Copyright and License Notice

Check for "license files"

  • Check 'about.html' files exists
  • are valid
  • have correct "layout" in directories
  • References:
In the general eclipse legal section
http://www.eclipse.org/legal/
Is one page that speaks to the about files directly
http://www.eclipse.org/legal/epl/about.php
In particular, note there are two that refer to literal HTML only versions, to use as your starting point.
http://www.eclipse.org/legal/epl/about.html
http://www.eclipse.org/legal/epl/longabout.html
Also, please read
http://www.eclipse.org/legal/guidetolegaldoc.php#Abouts
It goes into detail about the locations, needs for plugins and features, and also mentions that third party content requires a seperate license file.

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~244)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~398)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~2098)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3131)
All WTP Future Bugs (~422)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~205)
All API Requests (~9)


Back to WTP Meeting Archives

Focus on Backlog and Quality metrics (Neil)

Current Focus Item
  • Options are
  • Target bug for a release or "future"
  • Mark as Invalid or Wont Fix
Upcoming Focus Item
Past Focus Items
  • Invalid - Enhancement does not fit with the scope of the project or is already implemented.
  • helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.
  • Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.
  • Before July 1st, 2007 - 21
Where did they all go?
  • Minutes:
Neil: will focus on untargeted enhancements again after Release of 3.0

Back to the top