Hi Erik, On Feb 3, 2006, at 11:12 AM, [EMAIL PROTECTED] wrote:
- Release plans. We plan to cut a release at the end of the month. Everything we fix in JIRA should be marked as fixed in rc1. Michelle: we should do some formal release testing for rc1. AI Michelle propose a release test plan and start a wiki page.It means we have to release JPOX too.
Yes.
IMO a release candidate means no changes are planned before the final release unless a bug is found.
Yes.
Do you expect for this release all tests pass with JPOX ?
Yes.
Saying it differently, is the release dependent on JPOX results?
Yes, without all tests passing on JPOX there is no release.
Does it also mean that all unresolved spec issues will not be resolved?
I'll send out the list of unresolved spec issues and propose resolutions for all of them. There are not very many still outstanding by the way.
Craig
Regards, Quoting Craig L Russell <[EMAIL PROTECTED]>:Attendees: Michelle Caisse, Martin Zaun, Michael Bouschen, Michael Watzek, Matthew Adams, Craig Russell Agenda: 1. Test status (Michelle) 1154 tests, 4 failures, 2 errors. 2. Attach/detach tests (Matthew) no change. In fact Matthew will need to attend to some personal business and won't be working on these tests for a couple of weeks. Volunteers can take the code that's been checked in and work on it. 3. Other issues (any and all) - Release plans. We plan to cut a release at the end of the month. Everything we fix in JIRA should be marked as fixed in rc1. Michelle: we should do some formal release testing for rc1. AI Michelle propose a release test plan and start a wiki page. - Martin checked into the NoClassDefFoundError thrown during Class.forName. The result is that JDO implementations should catch not only ClassNotFoundException but in general LinkageError. Any of these Throwables should mean that the class does not exist. This issue came up during resolution of a name in a JDOQL query. The JDO implementation should use "class does not exist" to indicate that the name is not a class. JDO-194 has all the details. AI Craig: update the bug report and add a new test method for this condition. - JDO-246 variable in the query result. AI Craig: update the issue. - JDO is in the "incubator" category in JIRA. It should be in the"db" category. AI Craig: send a message to infrastructure to fix this.Action Items from weeks past: [Jan 20 2005] Debugging the regression we notice that some of the foreign keys in the Company model have generated names which makes it difficult to resolve the source of a key constraint violation. Schema0 through schema4 are affected. AI: Michelle to fix the schema. Done. [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. [Jan 20 2005] AI Craig look at new life cycle tests to see if it can fail at the end printing failure messages. AI Craig review the spec updates to make sure the test is consistent. AI Craig: resolve the test case and spec issues. [Jan 20 2005] AI Michelle update the JDO releases page to point to mirrors for download. AI Craig check in the released beta artifacts to the JDO maven repository (create a new releases directory parallel to trunk and branches). [Jan 13 2005] AI Martin look at the enhancement tests for completeness (JDO-64). [Jan 6 2005] AI: Michael: need to add a public static final field ina public class to test fully qualified class name static field in query.[Dec 23 2005] Query tests (Michael B) Looking at JDO-194 errors on Windows that don't happen on Linux. Might be a JRE bug. AI Martin file a Java bug so we know that there is a Java issue. [Dec 23 2005] Fetch depth discussion: The spec needs more information than is there in the PFD. AI Craig get more jdo experts involved in the discussion. In progress. [Dec 9 2005]: Nontransactional write semantics appear to differ between optimistic and datastore transactions. Is this intentional? AI: Craig discuss with expert group. Done. It is intentional. [Dec 2 2005] Inheritance 3 fails. Optimization of inheritance 1 where there is no table for abstract classes. JPOX doesn't support it. AI Craig: discuss this mapping with expert group. It might be an optional feature. [Nov 18 2005] AI: BEA to sign the donation paperwork for their test suite. Review how to merge their test cases into JDO TCK. [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5 issues. in progress [Oct 14 2005] AI: Michelle distill the mapping support that JPOX has into a list of features that are/are not supported. [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. [not done] April 15 2005] AI: Brian Topping will do the maven goal for creating and uploading the snapshots. He will create a directory parallel to trunk called "releases" and put the snapshots there. [May 13 2005] AI: Brian Topping will arrange for automated nightly builds. Craig RussellArchitect, Sun Java Enterprise System http://java.sun.com/products/ jdo408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
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
