::[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Web+Tools&product=WTP+Common+Tools&product=WTP+Datatools&product=WTP+EJB+Tools&product=WTP+Incubator&product=WTP+Java+EE+Tools&product=WTP+Releng&product=WTP+ServerTools&product=WTP+Source+Editing&product=WTP+Webservices&product=WTP+Website&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=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&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=target_milestone&type0-0-0=substring&value0-0-0=3.0.3 Number Fixed for 3.0.3] (~128)

+

::[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Web+Tools&product=WTP+Common+Tools&product=WTP+Datatools&product=WTP+EJB+Tools&product=WTP+Incubator&product=WTP+Java+EE+Tools&product=WTP+Releng&product=WTP+ServerTools&product=WTP+Source+Editing&product=WTP+Webservices&product=WTP+Website&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=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&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=target_milestone&type0-0-0=substring&value0-0-0=3.0.3 Number Fixed for 3.0.3] (~133)

:Java Server Faces

:Java Server Faces

Line 127:

Line 131:

* Minutes:

* Minutes:

−

<b>JSP Junit test failure</b>

+

<b>Blocker</b>

−

: Nitin: same test is added to the head branch, does not happen on local build at all, check on next build currently building

+

: Carl: currently investigating, working with JBOss

−

<b>Critical & Blockers</b>

+

<b>Hotbug </b>

+

:251908: Carl: deadlock issue, just opened, looking into it

+

:Kaloyan: not critical for this week, but need it for the 303

+

+

<b>Currently targeted bugs</b>

+

:Please triage, 112 currently for 303 while we're entering RC mode

== WTP 3.1 ==

== WTP 3.1 ==

Line 172:

Line 181:

=== Build & Smoketest ===

=== Build & Smoketest ===

* Build

* Build

−

::[http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20081016025007/I-3.1-20081016025007/ I-3.1-20081016025007] sent for smoketest

+

:: [http://build.eclipse.org/webtools/committers/wtp-R3.1-I/20081023110843/I-3.1-20081023110843/ I-3.1-20081023110843] sent for smoketest

−

:: [http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg06493.html Minor] version updates, all teams affected has reacted to these changes?

+

:: [http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg06493.html Minor] version updates done, all teams affected has reacted to these changes?

How can we better incorporate bugs-to-fix in 3.1 planning? Subsequent to meeting, I suggested that leads/committers should set the 3.1 milestone target for bugs that ideally should be fixed in 3.1, to help "prime the pot". For example, nearly all voted on bugs and "major" bugs should be so marked. I've added more bugzilla queries to WTP 3.1 Project Plan to assist.

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