Development Workflow: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
[[File:BugStatusStateDiagram.png]] | [[File:BugStatusStateDiagram.png]] | ||
* The bug reporting page also gets simplified as follows: | |||
[[File:BugReport.png]] | |||
Revision as of 16:30, 26 May 2011
This page summarizes the development workflow that was agreed upon at the ParaView Summit. The goal of this workflow is to organize ParaView development process making it easier for various projects contributing to ParaView to coordinate with each other as well as the release cycle.
The bug-tracker serves as the central tool that drives the process.
- A project is created for every customer/development team contributing to ParaView.
- Every task is must be reported as bug. When a issue is reported, if the issue is originating from a particular customer, the reporter will assign the issue to a particular project or leave it unassigned. If a customer gets interested in an issue, he can assign the issue to his project.
- A issue then moves over different states as described in the figure below:
- The bug reporting page also gets simplified as follows:
