> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > > > -----Original Message----- > > From: Diana Shannon [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, May 28, 2002 5:31 PM > > To: [EMAIL PROTECTED] > > Subject: Re: XMLForm howto live > > > > > > > > On Tuesday, May 28, 2002, at 09:24 AM, David Crossley wrote: > > > > > Hold on. I am not sure why we are wanting to publish > > > documentation onto the website about a feature that > > > is not available in the release. It is not even in the > > > upcoming 2.0.3 release. > > > > Thanks for catching this issue, David. > > > > This is going to make it *really* difficult to sync doc versions between > > branches (as well as the live site). I don't think we can maintain the > > distinction within FAQ files at the moment because they remain grouped > > by category. As for other docs, we'll have to come up with some kind of > > system to distinguish what How-Tos belong in what branch. Still, so much > > of syncing remains the result of an individual judgment call. If > > multiple committers are updating docs to both branches and the live > > site -- which they should, IMO -- well, we'll probably have mixed > > outcomes in spite of everyone's best intentions. > > > > We need community feedback on all docs, especially for new areas of > > Cocoon. How will we get it when the docs remain in head cvs? Also, > > community contributors need to see the results of their work on the live > > site, don't you think? If there's a delay, well, won't this discourage > > them? > > > > Why can't we commit all community-contributed docs to head, release, and > > the live site with *very clear* warnings regarding branch, when > > appropriate. We could enforce this within the howto.dtd and make it > > quite visible within howto2document.xsl, for example. I'll submit an > > example of this to what I've contributed to Forrest community structure, > > if you need to see what I mean. > > > There is only one drawback: if we make a 2.0.3 release from the branch, > the docs are perhaps not that upto-date because everything went into head.
All relevant documentation must be committed to both branches. If some (relevant to 2.0.3) docs are out of sync, they should be synced before release. Vadim > Carsten > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
