Category:Fix a Bug (Pathway)
(Difference between revisions)
(→Pathway Steps, Outcomes, & Learning Activities) |
(→Pathway Steps, Outcomes, & Learning Activities) |
||
| Line 71: | Line 71: | ||
:[[Finding_the_Code_Responsible_for_Behavior]] | :[[Finding_the_Code_Responsible_for_Behavior]] | ||
|- | |- | ||
| − | | 5. Submit patch to the community following community norms. | + | | 5. Submit patch to the community following community norms.(If patch is rejected, go back to step 4.) |
| Patch submitted to community | | Patch submitted to community | ||
| | | | ||
Revision as of 00:41, 9 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 |
|
| Git |
|
| 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. Find the buggy code | Specific lines of code in program identified | ||
| 4. Write and test code that attempts to solve the problem | Code written and tested for patch | ||
| 5. Submit patch to the community following community norms.(If patch is rejected, go back to step 4.) | Patch submitted to community | ||
| 6. 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.
