Hi, On 8/29/07, Jim Hurley <[EMAIL PROTECTED]> wrote: > Do other Apache projects typically: > - require code reviews (prior to integration)? > - require tests (prior to integration)? > - use JIRA for all changes (so they can be tracked), > or only for 'substantive' ones? > > It seems like that background might be helpful to making > a decision here.
It's typically up to each project to come up with the development practices that work best for them, and there are even projects that have different practices for different parts of their codebase (e.g. RTC for a stable core and CTR for experimental modules). As you noticed, there's no normative "Apache Development Process". If you've already used to doing code reviews, then it might make sense to start with the review-then-commit policy (RTC, see [1]) and perhaps relax that later. A typical workflow is that a patch is first attached to the respective JIRA issue and applied once (lazy) consensus is reached. [1] http://www.apache.org/foundation/glossary.html#ReviewThenCommit BR, Jukka Zitting
