On Wednesday, May 29, 2002, at 08:55 AM, Vadim Gritsenko wrote:
>>> >> 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. I agree. I don't want anything out of sync. What I'm asking is: Is it ok to commit community-contributed documents about non-release components/features to the web site as well as to the release branch AS LONG AS such documents will be clearly marked as such (with the visible warning text) when transormed. I will require version info (e.g. 2.0.3, 2.1, etc. ) inside each doc. A transformation step will determine whether a warning needs to be included in the displayed document content. As the release version changes, only a single xslt file will need updating. IMO, this will make it easier to sync documentation in both branches as well as on the live site. This means all community docs (regardless of version) will be committed to head and release branches, including the live site. Diana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
