:link to full documentation to the automatic IP Log, also available under project info, eclipse portal page, project leads should bookmark

:link to full documentation to the automatic IP Log, also available under project info, eclipse portal page, project leads should bookmark

Line 101:

Line 101:

:Tim: set the IPLog and + sign on the patch or the bug?

:Tim: set the IPLog and + sign on the patch or the bug?

:David: most specific thing, should do it on the patch, since patch only has 1 person's name attached to it

:David: most specific thing, should do it on the patch, since patch only has 1 person's name attached to it

−

:Kaloyan: still use contributed?

:Kaloyan: still use contributed?

Line 122:

Line 121:

:David: if it is not used should be make obsolete, if using a modified a version then yes okay to count as IPLog+, should also give feedback to the sumitter to better patch submission process

:David: if it is not used should be make obsolete, if using a modified a version then yes okay to count as IPLog+, should also give feedback to the sumitter to better patch submission process

−

<b>EclipseWorld</b>

+

:<b>EclipseWorld</b>

−

Attendance is way down from previous years, webtools classes was comparable to previous years, so still quite popular and well attended, material is available on the web, link posted

+

:Attendance is way down from previous years, webtools classes was comparable to previous years, so still quite popular and well attended, material is available on the web, link posted

−

<b>Eclipse Summit</b>

+

:<b>Eclipse Summit</b>

: upcoming: Kaloyan is presenting, Cameran for JSF

: upcoming: Kaloyan is presenting, Cameran for JSF

Line 194:

Line 193:

* Miinutes

* Miinutes

+

: SAP hotbug 251809: will have QA results tomorrow from SAP

+

: David: I'm good once the problem is good

+

: Tim: approve

+

: Chuck: likely to cause problems?

+

: Carl: code is passing through alot, but it is a specific area of fix is isolated

+

: will be checked into the build, while awaiting QA results tomorrow, Kaloyan will send out a note to releng with the results tomorrow. If bad, then will revert

== WTP 3.1 ==

== WTP 3.1 ==

Line 265:

Line 270:

* Minutes:

* Minutes:

+

: 10 Junit failure in XML encoding after moving up platform dependency. Platform bug opened, they will need to fix for M4, but does not need them to respin M3 for this malformed errorcases, Nick will be commenting out the Junit test for our M3 and referencing the bugzilla

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.

10 Junit failure in XML encoding after moving up platform dependency. Platform bug opened, they will need to fix for M4, but does not need them to respin M3 for this malformed errorcases, Nick will be commenting out the Junit test for our M3 and referencing the bugzilla

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