RE: Release preparations (was Re: createEntityReference issues)

> > 1. Do we provide separate distributables for Java and ECMAScript
> > bindings?
> >
> [dd] Open issue, no personal preference. I'd think it's 
> simpler to have 
> one distributable, but as I said, I have no personal preference.

Let's go for one distributable for both standard bindings.  Do we want a
.zip, .tar.gz or both?

> > 2. Do we include:
> >
> > A) DOMTSML test source
> >
> [dd] I think we should.

Not hurtful and shouldn't bloat the archive much.  If provided, should also
have dom1.dtd and dom1.xsd provided.

> 
> > B) Doxygen generated documentation for Java tests
> >
> [dd] Open issue, people's views?

The Doxygen generated output is both very useful in understanding the tests
and awkward for a casual user to generate on their own.  I'd recommend at
least having it as an optional download if not in the distribution archive.


> > C) Test matrix.  If so, would somebody like to pretty up the test 
> > matrix XSLT
> >
> [dd] I think we should, to give people an entry point to the DOM TS. 
> What is the XSLT in need of?

Style.  I believe the contents are technically accurate (other than the test
URL's being bogus) but everything is straight black-on-white HTML with no
copyright notices, introductory text, etc.  If the tests are going to be in
the distribution, then the test matrix links should refer to the local copy.
If doxygen output is in the distribution, then a link to the Doxygen page
for that test would also be nice.


> > 3. How do we handle the dependency of the JSUnit tests on 
> the relative 
> > location of JSUnit?  I've thought it might be technically 
> possible to 
> > eliminate that dependency, but I haven't spent serious time on it.
> >
> 
> [dd] I haven't been able to look into this either.

I'm going to post something on the JSUnit mailing list shortly and will
investigate tonight.

It would also be nice to be able to run the Java tests from the JUnit GUI
runner.  I'll take a look at adding classes that correspond to running the
Level 1 Core tests for specific processors and configurations.  So you could
start the Junit GUI runner, browse junit-run.jar and then select
TestDOM1CoreJAXPDefaultConfig1, TestDOM1CoreXercesConfig1,
TestDOM1CoreCrimsonConfig2, etc.

Also, it would be appropriate to add GNUJAXP to the .jar class paths.

Received on Monday, 28 January 2002 16:09:02 UTC