Category:Update a Tracker Issue (Pathway)

(Difference between revisions)
Jump to: navigation, search
(Created page with "__NOTOC__ '''The contributor will''': study and attempt to update a tracker issue (e.g. a bug report or feature request) to identify missing information, provide additional i...")
 
Line 11: Line 11:
 
| Software Configuration
 
| Software Configuration
 
|  
 
|  
−
* Download and install the development environment.
 
 
* Run the program.
 
* Run the program.
 +
* Possibly: Download and install the development environment.
 
|-
 
|-
 
| Issue Tracker
 
| Issue Tracker
Line 33: Line 33:
 
| 1. Select a tracker issue to update. For example:
 
| 1. Select a tracker issue to update. For example:
 
# an issue identified by the HFOSS community as appropriate for students.
 
# an issue identified by the HFOSS community as appropriate for students.
−
# an issue selected and assigned by the instructor.
+
# an issue identified (and possibly assigned) by the instructor.
 
# an issue selected by the student.
 
# an issue selected by the student.
−
| Issue is selected.
+
| You have selected an issue.
 
|
 
|
 
| [[Bug Selection]]
 
| [[Bug Selection]]
 
|-
 
|-
−
| 2. Study the issue details and identify possible clarifications.
+
| 2. Study the issue details and identify aspects that could be clarified.
 
: a. How could the issue's ''description'' be clarified?
 
: a. How could the issue's ''description'' be clarified?
 
:: i.  for a bug report, it is clear what goes wrong, and how to reproduce it?
 
:: i.  for a bug report, it is clear what goes wrong, and how to reproduce it?
 
:: ii. for a feature request, it is clear what could be better, and how it might work?
 
:: ii. for a feature request, it is clear what could be better, and how it might work?
 
: b. How could the issue's ''impact'' be clarified?
 
: b. How could the issue's ''impact'' be clarified?
−
:: i. How many users are affected?  
+
:: i. How many users are affected?  
 
:: ii. How important is it to these users?
 
:: ii. How important is it to these users?
 
: c. How could the issue's ''scope'' be clarified?
 
: c. How could the issue's ''scope'' be clarified?
−
:: i. What code, documentation, database, etc would be changed?
+
:: i. What code, documentation, database, etc would be changed?
 
:: ii. How difficult will these changes be?
 
:: ii. How difficult will these changes be?
−
| Possible clarifications are identified.
+
| You have identified one or more aspects that could be clarified.
 
|
 
|
 
|
 
|
 
|-
 
|-
−
|
+
| 3. Choose an aspect and try to clarify it.
 +
: a. If the ''description'' is unclear:
 +
:: i.  Search for more details - was the issue discussed in IRC, forums, other issues, etc?
 +
:: ii. Specify what is unclear and ask the reporter to clarify.
 +
: d. If the issue is a bug report, try to [[:Category:Verify a Bug (Pathway)|Verify a Bug]].
 +
: e. If the issue is a feature request, try to
 
|
 
|
 
|
 
|

Revision as of 17:16, 7 February 2017


The contributor will: study and attempt to update a tracker issue (e.g. a bug report or feature request) to identify missing information, provide additional information, or resolve the issue.

The contribution is: updated information about the issue, which could make it easier to address.

Prerequisites

Area The contributor must be able to:
Software Configuration
  • Run the program.
  • Possibly: Download and install the development environment.
Issue Tracker
  • Describe issue trackers and how they are used.
  • Access the issue tracker with appropriate permissions.
  • Read, create, and update issues in a tracker.
Community
  • Describe the community guidelines for management and triage of issues (bug reports and feature requests).

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. Select a tracker issue to update. For example:
  1. an issue identified by the HFOSS community as appropriate for students.
  2. an issue identified (and possibly assigned) by the instructor.
  3. an issue selected by the student.
You have selected an issue. Bug Selection
2. Study the issue details and identify aspects that could be clarified.
a. How could the issue's description be clarified?
i. for a bug report, it is clear what goes wrong, and how to reproduce it?
ii. for a feature request, it is clear what could be better, and how it might work?
b. How could the issue's impact be clarified?
i. How many users are affected?
ii. How important is it to these users?
c. How could the issue's scope be clarified?
i. What code, documentation, database, etc would be changed?
ii. How difficult will these changes be?
You have identified one or more aspects that could be clarified.
3. Choose an aspect and try to clarify it.
a. If the description is unclear:
i. Search for more details - was the issue discussed in IRC, forums, other issues, etc?
ii. Specify what is unclear and ask the reporter to clarify.
d. If the issue is a bug report, try to Verify a Bug.
e. If the issue is a feature request, try to
1. Read the bug report on the issue tracker.
i. If there is enough information to reproduce the bug. continue to step 2.
ii. Otherwise, use the issue tracker to ask the reporter for more information.
Exception: Couldn’t understand the report: ask the reporter for additional information using the issue tracker
Decision to proceed to the next step or a request for more information in the issue tracker.
2. Reproduce the bug
i. Run the program
ii. Follow the steps outlined in the bug report. If the steps cannot be followed, use the issue tracker to ask the reporter for clarification.
Exception: Procedure in bug report could not be followed: ask reporter for clarification using the issue tracker
iii. Observe the program’s behavior
Observation of program behavior or a request for more information in the issue tracker.

Reproduce a Bug Activity

3. Report results on the issue tracker Report posted to issue tracker.

Part of Reproduce a Bug Activity

Notes for Learning Activities Related to this Pathway

When creating activities:

  1. Use examples to demonstrate concepts to student.
  2. Use screen shots when possible.
  3. Prompt students to indicate the exact steps taken to replicate the bug.

This category currently contains no pages or media.

Retrieved from "http://foss2serve.org/index.php?title=Category:Update_a_Tracker_Issue_(Pathway)&oldid=8948"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox