::218281: DaveC: affecting adopter, only happens when there is a large# of includes, usibility point of view, it cannot be used from a day to day work

+

::Amy: Keith is looking at it and has been looking at it, has been there since 2.0, a usecase that was not addressed. Keith does have a fix, but it's an ugly and messy fix. Actively looking at it.

+

::Nitin: Not issue in a regular editor, accept the hotbug request and target to RC1/RC2

+

::DaveC: XSD editor specific

+

::DavidW: preventing an adopter from adopting WTP can be a hotbug request, we should look into it, but depending on risk may or may not make the release

+

::DaveC: Yep, need to have it looked at, but even in the next release M1 release that would be good too

:*M7 Criticals/Blockers

:*M7 Criticals/Blockers

−

::227501Valentin: will touch base with Kathy on the blocking bug

+

::228881: Carl: Jason has a patch out there, but hasn't asked for review. It is needed for M7. Not performance, but tools.

−

::225022: Neil, depending on the other bug on the list 225802

+

::Tim: Spec doesn't say, but jar input string asks it to be first otherwise it might blow up.

−

::225802: Chuck: always have unloaded in this situation, will definitely need to look at it, it could be due to timing, but that behaviour hasn't changed

+

−

::Neil: we can chat offline on this, set up mtg offline on this

+

−

::Neil:M7 blocking, fairly standard usecase, consistent deadlock, will need to look into it more to understand the frequency of it occuring

+

:*Untargeted blocker/criticals

:*Untargeted blocker/criticals

−

::227887

+

::229330: Konstantin: Just saw it. Not for M7, maybe RC1.

−

::Tim: Cannot run server when it's on a Arabic project name space.

+

−

::David: might have a remote machine

+

−

::More information is needed right now, possible it's a user error

+

−

::228472:

+

:*Reminders

−

::Tim: API breakage

+

::David:

−

::Helen: will shoot over a email to Konstantin

+

::1) No more builds until we declare unless it's a critical bug

+

::2) Note sent to releng: Need to generate Javadoc plugins for all components, target RC1

=== Release Review Requirements ===

=== Release Review Requirements ===

Line 166:

Line 176:

==== IP Log ====

==== IP Log ====

−

* In general, Project leads should review our [http://www.eclipse.org/webtools/development/ip_log.html IP Log] for completeness and correctness. Some big items/omissions are being tracked in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=228729 bug 228729].

:[https://bugs.eclipse.org/bugs/chart.cgi?category=-All-&subcategory=-All-&name=432&label0=Weekly+Open+WTP+Bugs+with+Patch+Attached&line0=986&datefrom=&dateto=&action-wrap=Chart+This+List All Open WTP Bugs with Patches Attached] (Graph)

:[https://bugs.eclipse.org/bugs/chart.cgi?category=-All-&subcategory=-All-&name=432&label0=Weekly+Open+WTP+Bugs+with+Patch+Attached&line0=986&datefrom=&dateto=&action-wrap=Chart+This+List All Open WTP Bugs with Patches Attached] (Graph)

−

:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&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&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=attachments.ispatch&type0-0-0=equals&value0-0-0=1&field0-1-0=attachments.isobsolete&type0-1-0=equals&value0-1-0=0 All Open WTP Bugs with Patches Attached] (~229)

+

:[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&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&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=attachments.ispatch&type0-0-0=equals&value0-0-0=1&field0-1-0=attachments.isobsolete&type0-1-0=equals&value0-1-0=0 All Open WTP Bugs with Patches Attached] (~205)

Performance Focus (Kaloyan)

Update 2008-03-06: We have identified that changes made in bug 201469 could be a potential reason for the Derby error:

ERROR 42Y07: Schema 'GUEST' does not exist

The changes in the bug are about improving performance, but they also affect the org.eclipse.test.internal.performance.db.DB class and if we compare between revisions 1.68 and 1.70 we could see that the changes deal with some user and password settings. Now it is not clear what should be changed in the WTP perf tests setup to comply with this change. May be setting some user and password for Derby?!

Update 2008-03-13: We have found an interesting article about Derby that seems to explain the problem. There it is explained that if the database is accessed without authentication, then the default database schema is APP. This is our case before the changes of bug 201469. But, if authentication is used, then the default schema becomes the username. After the changes of bug 201469 all access to the DB is done through the default user Guest. The DB driver tries to find the tables in schema GUEST instead of in schema APP. This explains the Error message above.

We see the best solution is to rename the schema in our Derby database from APP to GUEST for builds after bug 201469. We are now investigating how to do this.

Minutes:

David: Generate db with platform test plugin, then things are okay, asked for the earlier build to be restored in the update site. Making progress on this, hopefully will have more report in 2 weeks

Update 2008-03-27: DB issue resolved. Just setting DB user and DB password to "app" on newer builds solves the problem. We have now perf results for M3 and M4.

It seems that we have new problems with M5. It takes much longer (~33 hours compared to ~11 hours) and the wtpperflog is huge (120 MB) and full with dumps and errors. I need some time for further investigation of the problem.

Update 2008-04-10: The reason for the plugin start failure was that the xsd-runtime binary was not extracted by the procedure. This is now fixed. Other issues are faced. In M5 we have OutOfMemoryError, heap memory is now increased and tests are running again. In M6 we have StackOverflowError - probably a bug in the Platform.

Update 2008-04-17: I have increased the heap memory to 512 MB and now we have successful run for M5. However, there are still some test failures that need to be investigated. Need help here! For M6 the StackOverflowError is still valid. I have filed bug 227603 to the Platform.

API Tools/Scans (Kaloyan)

Current ones will be ending soon.
Kaloyan volunteered to explore the new Platform API tools, to make recommendations to WTP or build process.

Update 2008-03-06: I have started exploring and evaluating the Api Tooling project. It is planned to become part of Eclipse 3.4 by the end of M6. Now it is available only by checking it out from CVS.

The Api Tooling supports profiles. I need to check if this can correspond to our adopter usage reports.

There are also Batch mode tools: Binary Compatibility Reporting and API Usage Reporting, but I am still in progress to find out how to run them.

Update 2008-03-13: No progress this week. I will try to catch API Tooling developers at EclipeCon next week. They also have a Long Talk on the event.

Update 2008-03-27: I had the chance to meet Olivier Thomann. He explained me a lot about the API Tooling and gave useful advices. It seems that we would not be able to use API Tooling in the way we use our adopter API scannages. The concept of API Tooling is different. Instead we can compare for binary and source breakages between WTP releases, e.g. between 2.0.1 and 2.0.2.

Adopting API tooling requires some efforts. It is almost sure that enabling a plugin with API tooling nature will introduce lots of warnings and errors. Rules and filters must be established within the code to prevent this warnings to appear.

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.

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.