* 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?)

*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.

:[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)

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

−

+

:;*[[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.

+

:::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.

:: 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 213:

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

WTP 3.0 End-Game

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.

WTP 3.0.1

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

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

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.