On Thu, 2002-03-21 at 07:50, [EMAIL PROTECTED] wrote: > Hi Andy, > > > > >I don't like just relying on a series of simple text files > like TODO, STATUS, etc. I would like it organized into a nice > cohesive set of HTML docs.
I don't care how it's organized as long as we use it and keep it up to date > I'm not sure I like text files either, but release preparation is not > something even advanced users will be interested in. Nonetheless, a faq > entry on patch submission would, at the very least, certainly be > appropriate somewhere in our documentation. So perhaps, as an interim > measure until we reorganize the docs, we can dcreate a faq-contributing and > put all this stuff in there. > > >> build.xml > > >The list of changes should be enumerated. > > Sure. +1 > >> docs/releases.xml - be sure to give contributors credit for their > work > > >This file should be updated every time that a considerable > Of course; and perhaps a note to this effect would be good. But the > release manager still needs to take a pass through what's there and make > sure, as best s/he can, that nothing big is missing. ++1 > >We should explain how to move the existing tag number up > when last minute bug fixes have gone into the code base > (the "cvs tag -f ..." command). > > I'm not sure this isn't starting to boil the ocean; so maybe you can do > this once this is in CVS. :-) > > >> Do a test build and regression test run > > i.e., build test at a bare minimum > > >Which tests are you referring to? The limited regression > tests that we have in CVS? or the XML conformance suite at > OASIS using David Brownell's driver? > > The former. I don't want to be too much more prescriptive about what tests > to run, since there are lots of suites one could use, but not all release > managers will have access to them. We've got the Sun CTS suite here, for > instance, but I don't think most folks will have gone to the trouble of > setting up a full J2EE environment. :-) Besides, it would be nice to > think that, over time, our CVS test infrastructure will grow and mature to > something like what xalan has. > I've been toying with the idea of getting some more testing into the build system. I was thinking of trying to have the build scripts go fetch the OASIS suite and any appropriate software and run it through. I was also thinking of trying to get the W3C schema test suite, until I looked through it -- it seems very disorganized and would be a big effort to get going. If the JSPA changes go through, I am assuming that we will be able to get a copy of the binary TCK for JAXP. If people think this is a good idea, I'll start taking a look at this in the 2nd week of april. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
