[vtk-developers] VTK code review / testing / integration workflow

[Berk Geveci]

Here is a summary that I came up with from the discussion so far. Does this
look good?

Requirements:

- Branch / topic based workflow
- Automated testing before merge (required to pass)
- Assign reviewers to topic
- Review / approval before merge (required to pass)
- Ability to go back to discussion leading to merge (audit trail)
- Automatic notification on change
- Ability to comment on the code (Web GUI preferred)
- All reported bugs should be assessed and assigned

Nice to have:

- Tight integration with issue (bug) tracking and release process
- Stakeholders for particular pieces identified / in the loop / easy or
automatic assignment of
reviewers
- Ease of use
- Incentive for reviewers (goal being encouraging more reviews)
- Integration with Wiki
- Easy documentation / Markdown /rST support
- Easy way to generate single view of all changes in the Web GUI
- Lightweight proposal process for large changes
- Way to track performance regression
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20140826/5860c966/attachment-0002.html>