Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 21720 invoked from network); 2 Oct 2006 23:29:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Oct 2006 23:29:59 -0000 Received: (qmail 7235 invoked by uid 500); 2 Oct 2006 23:29:59 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 7224 invoked by uid 99); 2 Oct 2006 23:29:59 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2006 16:29:59 -0700 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=HTML_MESSAGE Received: from [192.18.42.249] ([192.18.42.249:29409] helo=nwk-ea-fw-1.sun.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 2B/30-29668-4F0A1254 for ; Mon, 02 Oct 2006 16:29:57 -0700 Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k92NTrdZ009380 for ; Mon, 2 Oct 2006 16:29:53 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0J6J009017V4DJ00@d1-sfbay-09.sun.com> (original mail from Craig.Russell@Sun.COM) for jdo-dev@db.apache.org; Mon, 02 Oct 2006 16:29:53 -0700 (PDT) Received: from [192.168.0.10] (c-24-6-172-77.hsd1.ca.comcast.net [24.6.172.77]) by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0J6J00LBW7XSX550@d1-sfbay-09.sun.com> for jdo-dev@db.apache.org; Mon, 02 Oct 2006 16:29:53 -0700 (PDT) Date: Mon, 02 Oct 2006 16:29:47 -0700 From: Craig L Russell Subject: Test Case Challenge Process Sender: Craig.Russell@Sun.COM To: Apache JDO project , JDO Expert Group Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.752.2) Content-type: multipart/signed; protocol="application/pkcs7-signature"; boundary=Apple-Mail-39--1011520484; micalg=sha1 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Apple-Mail-39--1011520484 Content-Type: multipart/alternative; boundary=Apple-Mail-38--1011522042 --Apple-Mail-38--1011522042 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed There are currently 14 challenges filed by BEA that need to be resolved within 15 working days of receipt. From the TCK RunRules document that is part of the official JSR release, the first level TCK Challenge process includes the following: If any test does not pass on the JDO implementation under test, this may be due to an error in the implementation or in the TCK test. If you believe that the failure is due to an error in the TCK test, you may challenge the test. To do so, send email to: jdo- dev@db.apache.org with a subject line containing "CHALLENGE" and the name of the test program, e.g. org.apache.jdo.tck.api.persistencemanager.ThreadSafe.java; and the body of the email containing the details of the challenge. The Maintenance Lead will respond within 15 working days with a decision on whether there is an error in the test case. If the issue is found by the Maintenance Lead to be due to an error in the test case, the Maintenance Lead might provide a patch that will be included in the next maintenance revision. If the patch is not provided within 15 working days of the receipt of the challenge, then the test may be put into the TCK directory src/conf/exclude.list and it will not be run as part of the TCK. Decisions of the Maintenance Lead may be appealed to the full expert group. A vote of the full expert group will be conducted by the Maintenance Lead, and a majority of votes cast will decide the issue. The Maintenance Lead has one vote, as does each member of the expert group at the time of the vote. I'd like to propose a process for handling the test case challenges. I've created a branch https://svn.apache.org/repos/asf/db/jdo/ branches/2.0.1 into which we can put the patches referenced by the process. This allows us to manage patches that might differ from the trunk. This is necessary in case we want to modify a test case because the specification is unclear, but change the specification instead of changing the test case. A wiki page has been created to track the TCK challenges http:// wiki.apache.org/jdo/TCKChallenges?action=show which can be updated by anyone. The JIRA that tracks each challenge is identified here. Fixes that have already been committed to the trunk will be merged into the 2.0.1 branch. The challenger should check out the 2.0.1 branch and verify that the fix as identified in the JIRA is ok. If there is an issue with the fix, the JIRA should be updated with comments. If a resolution is not acceptable by the challenger, then an appeal to the entire expert group should be filed. Comments? Craig Russell clr@apache.org http://db.apache.org/jdo --Apple-Mail-38--1011522042 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
There are currently 14 = challenges filed by BEA that need to be resolved within 15 working days = of receipt.

=46rom the TCK RunRules = document that is part of the official JSR release, the first level TCK = Challenge process includes the following:

<spec>

If any = test does not pass on the JDO implementation under test, this may be due = to an error in the implementation or in the TCK test. If you believe = that the failure is due to an error in the TCK test, you may challenge = the test. To do so, send email to: jdo-dev@db.apache.org with a subject line = containing "CHALLENGE" and the name of the test program, e.g. = org.apache.jdo.tck.api.persistencemanager.ThreadSafe.java; and the body = of the email containing the details of the challenge.

The Maintenance Lead will = respond within 15 working days with a decision on whether there is an = error in the test case. If the issue is found by the Maintenance Lead to = be due to an error in the test case, the Maintenance Lead might provide = a patch that will be included in the next maintenance revision. If the = patch is not provided within 15 working days of the receipt of the = challenge, then the test may be put into the TCK directory = src/conf/exclude.list and it will not be run as part of the = TCK.

Decisions of the = Maintenance Lead may be appealed to the full expert group. A vote of the = full expert group will be conducted by the Maintenance Lead, and a = majority of votes cast will decide the issue. The Maintenance Lead has = one vote, as does each member of the expert group at the time of the = vote.

</spec>

I'd like to propose a process for handling the test = case challenges.=A0I've created a branch https://sv= n.apache.org/repos/asf/db/jdo/branches/2.0.1=A0into which we can put = the patches referenced by the process. This allows us to manage patches = that might differ from the trunk. This is necessary in case we want to = modify a test case because the specification is unclear, but change the = specification instead of changing the test case.=A0

A wiki page has been = created to track the TCK challenges=A0http://wik= i.apache.org/jdo/TCKChallenges?action=3Dshow which can be updated by = anyone. The JIRA that tracks each challenge is identified here. Fixes = that have already been committed to the trunk will be merged into the = 2.0.1 branch.

The challenger should check = out the 2.0.1 branch and verify that the fix as identified in the JIRA = is ok. If there is an issue with the fix, the JIRA should be updated = with comments. If a resolution is not acceptable by the challenger, then = an appeal to the entire expert group should be = filed.

Comments?

Craig = Russell
clr@apache.org http://db.apache.org/jdo

= --Apple-Mail-38--1011522042-- --Apple-Mail-39--1011520484 Content-Transfer-Encoding: base64 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGUDCCAwkw ggJyoAMCAQICEB7Y7fLHmKoeHTUdbtYrvpAwDQYJKoZIhvcNAQEEBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA1MTIxNTIxNDc0NFoXDTA2MTIxNTIxNDc0 NFowbDEQMA4GA1UEBBMHUnVzc2VsbDEUMBIGA1UEKhMLQ3JhaWcgTGFpcmQxHDAaBgNVBAMTE0Ny YWlnIExhaXJkIFJ1c3NlbGwxJDAiBgkqhkiG9w0BCQEWFUNyYWlnLlJ1c3NlbGxAU3VuLkNPTTCC ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMXXgEAm88nu8cFbxXSWqTq+GaYpCx/0QSom 8kBbVxpJIURuO4ErLDupeXu6y9+5e7ZKLbeSQE5xbfYPcQR/IhqmYKy5YqRcuzPXREBj2zKEkZph pNXWpHgMdx9W8dq0Cu2i9Ux/S6c2MuEHrP6gfGGll+b/mzLoO280QHTuE4pcpKntRnwZdGxQ/5l8 IL+eLP+jpJAbYW9C+KNKofZtS6V6R0uzlqTOsEdZvwxZQ4mmPgHoz1+Gjwme/PC5sKvF09MaJDiI pj9SvZ4CTCgcDZV78J086YwlVbMC0VQotjhu1p42lr8CS33IXLz3OWNrDETCAepah/Dgw2ZZApQ9 9L0CAwEAAaMyMDAwIAYDVR0RBBkwF4EVQ3JhaWcuUnVzc2VsbEBTdW4uQ09NMAwGA1UdEwEB/wQC MAAwDQYJKoZIhvcNAQEEBQADgYEAKdIkgAWCg2Bi7ocnstfJA4iymTRI2/L4oQx9zvllM9bNJ2cR cecJIx3HuoHbhPvemh1GExEPgHU+dXSxDmD0BEmPnhSReKCURyslnbMphPZ5kR6USzQFrRa+v0ii J+SBO9VQYTQWT+xEjmRLM76MfkBFw3IOC9CUkRoYZ88pOoUwggM/MIICqKADAgECAgENMA0GCSqG SIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQH EwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZp Y2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1h aWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMw NzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls IElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUE cJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/Ef kTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMB AAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3Js LnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYD VR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GB AEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+ hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC 3CEZNd4ksdMdRv9dX2VPMYIDEDCCAwwCAQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0ECEB7Y7fLHmKoeHTUdbtYrvpAwCQYFKw4DAhoFAKCCAW8wGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDYxMDAyMjMyOTQ4WjAjBgkqhkiG9w0B CQQxFgQUOX4/11atMemeTCUwVd8kQd7BQuAwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMC WkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAe2O3yx5iqHh01HW7WK76QMIGHBgsqhkiG 9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAe 2O3yx5iqHh01HW7WK76QMA0GCSqGSIb3DQEBAQUABIIBAEEUWbMHFZnMHDlxKMpYHEEv8Hgs+q3T AEjdf9G2Z0iHtPfT9TtB6ociB01VEWxv9MRQlSZAYVFk7padZpw+7MtmiEYJ29NO8nDCBvQsSbwj zqehTYJyuHpptGnHEaQIozQ4YF5wuXsa+c9fH/JqO55zcD98aRDVWPi/CSivmup+eify+CgetC0y 9DK5QfsgiwaGcTBErEpdYkQBmdLg/WGzikkzimE4kECom9NEMZIiAcOh/yFnuN4seZUWCGecLCTr 9KPepGLbEO68sHFpqtoEeYosKM3bMX3++mT02yImcPuMnyFgNROhaOPpsnubg35ofOwHg8HjHoFv RwxqHQMAAAAAAAA= --Apple-Mail-39--1011520484--