Bug Tracker Workflow

From ParaQ Wiki
Revision as of 10:54, 1 July 2010 by Utkarsh (talk | contribs) (Created page with 'This is a proposal for changes to bug-tracker to implement a software development process into ParaView development. =Goals= * Easier to report bugs * Easier to identify bugs we…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

This is a proposal for changes to bug-tracker to implement a software development process into ParaView development.

Goals

  • Easier to report bugs
  • Easier to identify bugs we are focusing on for next release (major as well as patch)
  • Easier to identify bugs being worked on currently
  • Easier to identify who's working on what
  • Easier to mark/identify the active pool

User Permissions

For this document let's assume following user categories.

  • reporters -- anyone, people who report bugs.
  • developers -- people who fix bugs (including testers)
  • managers -- people who decide what bugs to work on and who should work on them

Reporting Bugs

  • Currently there's simple and advanced view for reporting bugs.
  • Reporters should just see the following:
 Category: <bug/feature>
 Product Version: <what version this bug is present it>
 Summary: <brief summary>
 Description: <bug description>
 Upload File: <attachments>