Category:Fix a Bug (Pathway)
(Difference between revisions)
(→Pathway Steps, Outcomes, & Learning Activities) |
(→Pathway Steps, Outcomes, & Learning Activities) |
||
| Line 56: | Line 56: | ||
* [[:Category:Written Communication|Writ Comm]] | * [[:Category:Written Communication|Writ Comm]] | ||
* [[:Category:Management|Mgmt]] | * [[:Category:Management|Mgmt]] | ||
| − | | | + | | :[[Document_Code_with_Meaningful_Comments_(Activity)]] |
|- | |- | ||
| 4. Once accepted or abandoned verify that the issue is updated appropriately | | 4. Once accepted or abandoned verify that the issue is updated appropriately | ||
Revision as of 19:22, 8 March 2017
The contributor will: fix a bug by submitting a patch and updating the issue tracker.
The contribution is: a patch for the bug and updated information in the issue tracker.
Prerequisites
| Area | The contributor must be able to: |
|---|---|
| Software Configuration |
|
| Issue Tracker |
|
| Community |
|
Pathway Steps, Outcomes, & Learning Activities
Follow the project’s policies and practices to complete the steps below.
| Pathway Step | Step Outcome | Process Skills Focus | Related Learning Activities |
|---|---|---|---|
| 1. Verify bug (see Verify a Bug (Pathway)) | Bug reproduced | ||
| 2. Claim issue on issue tracker | Issue tracker updated | ||
3. Repeat until change is accepted or abandoned:
|
Submitted patch and updated tracker | :[Solving_A_Bug] | :Document_Code_with_Meaningful_Comments_(Activity) |
| 4. Once accepted or abandoned verify that the issue is updated appropriately | Issue updated in issue tracker |
Notes for Learning Activities Related to this Pathway
When creating activities:
- Indicate the level of programming experience needed.
This category currently contains no pages or media.
