Diana Shannon wrote: > > On Friday, May 24, 2002, at 08:49 AM, Matthew Langham wrote: > > > The current Cocoon website documentation contained in CVS contains a > > structure that includes links to books, trainings etc. This sort of > > information (including links to Cocoon consultants, use-cases, best > > practices etc.) is getting more important as Cocoon becomes more widely > > used. > > > > What about updating xml.apache.org/cocoon to reflect this? > > Sure. It's my understanding, from Carsten, that any committer can update > the live site. If someone can provide instructions, I'd be happy to do > this for links now (and soon for lots of other docs in process). Then > I'll write a committer how-to to clarify the process for other/future > committers.
There is already a short description at http://xml.apache.org/guidelines.html, add the answer from Steven and that's all. > > Seems we have a provisional CMS here for *new* docs. Commit to head for > new documents, and wait a week or so for comments. After that, commit to > release and update live site. Is that your understanding? > Hmm, I'm not sure about that, maintaining both branches is not so nice, but perhaps it's for now the best way which means all docs which can be put on the website should go into the 2.0.3 branch as well and we can update it from there. > What about existing docs? Reading cvs commits, I can see updates to > existing docs in head, but not always a corresponding update to the > release branch. It would help greatly if we could at least keep existing > doc versions in sync. As for updating the live site, perhaps we could > schedule weekly updates (if no other new doc addition triggers the live > site update). > Yes, keeping them in sync is a good idea. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
