Attendees: Michelle Caisse, Michael Bouschen, Martin Zaun, Craig Russell
Agenda:1. Test status (Michael) 1239 tests 0 errors 2 failures 2 of 57 configurations fail. The persistent interface test is the only test that fails (both application and datastore identity). The symptoms of the failure have been changing, indicating progress is being made on the issue. The latest is that the class created for the persistent interface is not found. Either it wasn't created, it was created with the wrong name, or it was created in the wrong classloader.
2. Issues with staged release (any and all) JDO-356 has two doc issues to be fixed. JDO-293 has some spreadsheet issues to be updated before release. And JDO-327 (JPOX bug) needs to be resolved.
3. Integration and testing of JDO 2.0 release (Craig, others) The plan is to respin just the tck20 once changes are made to the documentation (not the code).
4. Other issues (any and all)JPOX needs a release of JDO 2.0 api in order to release their 1.1.0- rc-2. AI Craig: call for a vote to release just the API20 project to allow us to publish the API20 project, including publishing the jar files on ibiblio.
We would like to add a link from the JDO web site to the JIRA page to do calculations of the open and closed issues by release. AI Craig: make sure that all JIRA issues have a "resolved in release" entry. Might have to reopen some JIRA issues just to add this info. AI Michelle: add links in the web page to point to JIRA "open issues for xxx release" and "resolved issues for xxx release".
Assertions: Martin reviewed the assertion spreadsheet and commented extensively. Assertions that are exclusively lifecycle transitions should be marked as duplicate. AI Michelle: incorporate Martin's comments into the spreadsheet before Craig respins the release.
The coverage report should reflect the status of the released code. AI Michelle: copy the coverage.txt from the branches/2.0-rc1 into the branches/2.0 and update the statistics.
Action Items from weeks past:[Mar 24 2006] Craig has instructions on creating a release, and will add a wiki page with the instructions in case anyone else has an itch to make a release. In progress.
[Mar 24 2006] Need to resolve serialization of a detachable instance for durable storage. AI Craig: propose a solution for the specification. Done.
[Mar 17 2006] Remaining issue: datastore identity strategy is currently defined as IDENTITY but some datastores don't support IDENTITY columns. AI CraIg: propose a solution. In progress
[Feb 3 2006] AI Michael W fix list of teardown classes in company model reader. JDO-285. But this fix cannot be checked in until JPOX is fixed. Done. Will look at this for maintenance.
[Nov 18 2005] AI: BEA to sign the donation paperwork for their test suite. Review how to merge their test cases into JDO TCK. The latest news in BEA is that BEA plans to donate their object persistence engine to open source; it's not clear where they will do this, perhaps in Apache as a sister project to Apache JDO. BEA's OpenJPA is currently under consideration in the Apache incubator, so the integration work might be facilitated once this is resolved. Done. Too late.
[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5 issues. in progress
[Sep 2 2005] AI: To recruit members, update the web site. Articles on TheServerSide directing attention to the site. T-shirts, logo. AI: Craig write a ServerSide article.
[July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated to include all JDO metadata elements and attributes. Too late.
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
