Nicola Ken Barozzi wrote: > David Crossley wrote: > ... > > 2) The Forrest build system is complex. It would be good to automate > > the publishing of DTD versions, but that may not be possible. > > Could you please explain a bit more?
I was mainly hinting that it might need to be a manual task. > If it's just about placing the > schema dir, or some of those dirs, in a predefined place, > it can be done quite easily. It is only the /dtd/ and /entity/ dirs. These might also need to be re-arranged in xml-forrest CVS so that dumb clients can find all the bits properly. > > 3) The Forrest website is built using the "stable" version of > > Forrest (currently v0.5.1). So how will DTDs from the current > > CVS (v0.6-dev) get into the website CVS [3]? Manual copy? See 4). > > Aaah, so you want to publish them on the site CVS (I was thinking of > pushing them to the site, but you are right)... I am just trying to meet the requirement that all Apache website content needs to be managed in the project's website CVS. We also need to get any stable DTD stuff that is still in 0.6-dev out to the website. > > 4) If some committer changes the DTDs in CVS then they will be > > out-of-sync. Will committers remember to do the manual copy? See 3). > > I can check and make sure that the build system tells the committer to > do so, or a script that checks every night for consistency can be done. Either one would be good. --David
