Category:Fix a Bug (Pathway)
(Difference between revisions)
(→Pathway Steps, Outcomes, & Learning Activities) |
(→Prerequisites) |
||
| Line 18: | Line 18: | ||
* Access the issue tracker with appropriate permissions. | * Access the issue tracker with appropriate permissions. | ||
* Read, create, and update issues in a tracker. | * Read, create, and update issues in a tracker. | ||
| + | |- | ||
| + | | Git | ||
| + | | | ||
| + | * Understand how to find repository | ||
| + | * Fork the repository to your github account | ||
| + | * Clone the repository to your local github | ||
|- | |- | ||
| Community | | Community | ||
Revision as of 00:04, 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. Repeat until change is accepted or abandoned:
|
Submitted patch and updated tracker | ||
| 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.
