W3C home > Mailing lists > Public > www-dom-ts@w3.org > June 2001

SV: [General] domconftest now a project at SourceForge

From: Dimitris Dimitriadis <dimitris.dimitriadis@improve.se>
Date: Thu, 28 Jun 2001 20:04:37 +0200
Message-ID: <9F67DC27F4CCD311ABA600508B6A66A44A6A4B@VXOIMP1>
To: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
I definitely agree. However, we've known for some time that the primary
place for browsing and downloading tests, transforms and schems would be the
W3C site. SF came into the question as an alternative to W3C as far as
bug/issue tracking was concerned.

I realise that keeping tests and other resources on two different locations
can be tedious, but it may be a price that we have to pay (especially
myself, since I'm going to manually check in tests to SF if there are issues
about them).

/Dimitris

-----Ursprungligt meddelande-----
Från: Arnold, Curt [mailto:Curt.Arnold@hyprotech.com]
Skickat: den 28 juni 2001 19:50
Till: 'www-dom-ts@w3.org'
Ämne: RE: [General] domconftest now a project at SourceForge


My primary interest in getting the SourceForge project going was getting the
tests, transforms and supporting resources in a common CVS, so we could
automate the transform/compile/run cycle and
collaborate on fixing either the tests or the transforms.  

The initial hurdles for test correctness are schema/DTD validity and whether
the generated code successfully compiles.  If the tests and the transforms
are all in one CVS, then it should be fairly
simple to automate the process and iteratively fix problems.  Having the
tests and transforms in distinct locations definitely complicates matters,
especially since both are evolving.
Received on Thursday, 28 June 2001 14:05:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:44 GMT