New and Noteworthy to complete by 3pm EST tomorrow, Nitin will remove components with no information

Dali 2.1

Releasing tomorrow 12/19

New and Noteworthy?

Minutes:

Neil: Have been testing on the update site, found 1 feature version dependency issue affecting one of the update site scenarios, the same bug that was released for M4 and 2.1, all other update site tests are fine. All other function testing are good, will go ahead with the release tomorrow. Will put together a new note and worthy, everything are the same with the 3 milestones for 3.1

David: testing the update locally?

Neil: if you could upload the latest 2.1 bit on the site?

David: Do you have a build currently ready?

Neil: need to wait for the new one, latest one with the change had a DNF Junit, new build should be available before 3pm. Thanks!

Other business

David: yes had a couple of email exchanges. They recognize might be the best course of action even though may not like it, clarification needed should they expect any problems with the workaround posted in the bug. Haven't heard of any other adopters respond to Carl's note, no known cases that affects anyone else

Kathy: Has anyone noticed the really slow startup of eclipse?

Neil, Valentin, David: yes

David; will open bug to platform, suspect p2 issue with increasing # of plugins to load

Teams Status and Focus for Coming Week

Performance Team

The minutes of the meetings are posted.
Next meeting is next Monday same time. See details on the wiki page:
WTP Performance Tests

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