On Wed, Oct 6, 2010 at 7:12 AM, Mike Edwards <[email protected]> wrote: > On 04/10/2010 07:56, Luciano Resende wrote: >> >> Yes, that's what I'm doing for M5.1. For next releases, I was >> wondering if we should have a better strategy either by working with >> OASIS or by removing all of the compliance tests from the final >> release. It also makes me wonder if Oasis will give us any thing that >> says we "passed" the compliance tests. >> > Luciano, > > In a word - "no". > > OASIS is not into the game of verifying compliance. > > OASIS provides the testcase suite - it is up to runtime providers to take > the test suite, run it against their runtime and then claim conformance if > the runtime passes the tests. > > Note that the system of "policing" of this approach to conformance is the > simple one of making the testcase suite available to all, so that runtime > customers could do the same thing and thus verify the claims of any runtime > provider. > > > Yours, Mike. > >
Then we need a better repeatable way to provide these tests to customers in a Tuscany release, and it might be that we don't want to make them part of the release until there is an official release from OASIS, otherwise it's not repeatable. My experience with working with M5.1 is that, from the time we shipped M5 to now, things changed and running those tests were not doable anymore. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
