Chad Walters wrote:
One Apache process question: Should Wiki updates and additions like this flow through JIRA as well? If so, can we assume that documentation changes like this will follow a Commit Then Review model?
The wiki, since it is world-writable, is not an official Apache product, and is not subject to Apache processes, licensing, etc. Documentation that is maintained in subversion and is bundled into releases is part of an Apache product and is managed by Apache processes, licensing, etc.
Many projects have both a Wiki and official documentation. The wiki is an informal scratchpad for tips, tricks, etc. Official documentation is frequently authored in XML that's rendered as HTML (and PDF) by tools like Forrest and Anakia. It's versioned and branched with the code, so that one need not manually maintain different versions as one would on the wiki.
Some projects maintain their official documentation using the Confluence wiki, providing write-access only to committers, and exporting read-only copies for use as end-user documentation.
So, to answer your question, no, Thrift wiki updates do not need to flow through Jira. However documentation changes that will be distributed with releases should follow the same processes as code changes.
Doug
