The bugtracker and git: Difference between revisions
From LimeSurvey Manual
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
2. Bug assigned to developer (by the developer himself or someone else) | 2. Bug assigned to developer (by the developer himself or someone else) | ||
3. Bug fixed | 3. Bug fixed github.com | ||
4. | 4. Issue assigned to LimeSurvey repository owner (c_schmitz), status set to resolved. | ||
5. | 5. When a new version is released c_schmitz closes the resolved bugs. | ||
This method of working should allow for efficient bug fixing with multiple developers without getting c_schmitz overworked..? | This method of working should allow for efficient bug fixing with multiple developers without getting c_schmitz overworked..? | ||
Please respond on what you think of this process, or what should be changed. | Please respond on what you think of this process, or what should be changed. | ||
Revision as of 14:40, 9 August 2012
This article should help developers on the LimeSurvey when resolving issues.
General process outline.
1. Bug reported by user.
2. Bug assigned to developer (by the developer himself or someone else)
3. Bug fixed github.com
4. Issue assigned to LimeSurvey repository owner (c_schmitz), status set to resolved.
5. When a new version is released c_schmitz closes the resolved bugs.
This method of working should allow for efficient bug fixing with multiple developers without getting c_schmitz overworked..?
Please respond on what you think of this process, or what should be changed.