WTP Development Status Meeting 2008-07-10

Attendees

Announcements And Reports

JEE Meeting Report:

WTP support for Java EE 5 modules in a 1.4 level EAR is too big to contain in a maintenance release- will be a line item for WTP 3.1.
There will be more meetings about this, agenda/minutes will be posted on the wiki.
Next Meeting: July 24, 2008 at 11 am EDT

Minutes: Minutes of JEE Meeting will be posted soon, as well as call-in info for next call. The topic will be planning for WTP 3.1.

releng

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