> quotes Shane:
>One admitted difficulty with xml-xalan is that the 1.x code was
>rooted at the top level, which makes it hard to separate from other
>bits of Xalan.
A great example of how poor planning hurts you down the road. I am
adamantly opposed to saying "Let's just do it; we can fix it later"
when we know that we *will* have to fix it later. We knew at the
time we created that tree that we'd have other flavors!
>-- I'd like to see a decent vote/comment period go by, and then unless
>anyone complains, a backup...removal....
>Note that this includes each of the following areas in
>/home/cvs/xml-xalan:
> xml-xalan/* files (we should re-commit a README here that points
> users to each individual subproject and to the tests)
> xml-xalan/bin
> xml-xalan/docs
> xml-xalan/samples
> xml-xalan/src
> xml-xalan/xdocs
I think we should retain anything that applies across all flavors of
Xalan. Maybe some of the docs belong here? How about source files for
the flavor-independent Web pages? I suppose that has implications for
CVS, but is it really a problem or an opportunity?
.................David Marston
