New Issue Resolution Process
Shaddy Zeineddine <
shaddy@...>
2008-07-23 22:21:18 GMT
Steps (http://trellislms.org/wiki/DeveloperGuide):
1. Issue is identified: Anyone can identify an issue whether it be a
bug, a tweak, or a new feature.
2. Identifier analyzes and reports the issue: Once the issue is
identified, the person who identified the issue must collect as much
information as possible to submit a complete report in the tracker.
3. Issue is confirmed: Once the issue is reported, a lead developer will
review the report and confirm the issue if it is valid, adding any
useful information to the report.
4. Issue is discussed: If the issue is not a straightforward bug fix,
the issue will be discussed by the developers to determine an
appropriate solution.
5. Issue is assigned to a developer: Based on the urgency of the issue,
a lead developer will decide when and to whom to assign the issue.
6. Developer makes changes to development repository: Once a developer
has been assigned to an issue, the developer will make the necessary
changes to the development repository and test the changes. After the
developer is satisfied with the changes, the developer will notify the
maintainer by sending a reminder from the issue tracker. The reminder
should include any information which will help the maintainer understand
the changes.
7. Changes are reviewed by the maintainer: The maintainer will review
the changes and determine if the changes have resolved the issue and
(Continue reading)