Write a Bug Report (Activity)
(Difference between revisions)
Rmezei (Talk | contribs)
(Created page with "__NOTOC__ {| border="1" |- |'''Title''' || Writing a Bug Report |- |'''Overview''' || In this part, students will gain some basic knowledge about bug tracking systems,...")
Newer edit →
(Created page with "__NOTOC__ {| border="1" |- |'''Title''' || Writing a Bug Report |- |'''Overview''' || In this part, students will gain some basic knowledge about bug tracking systems,...")
Newer edit →
Revision as of 14:01, 27 May 2015
Title | Writing a Bug Report |
Overview | In this part, students will gain some basic knowledge about bug tracking systems, and how that can be used in FOSS projects. Students will also check and confirm the existence of a reported bug (both in a stable version, and in an unstable version), and report out their findings using Bugzilla. |
Prerequisite Knowledge | |
Learning Objectives | Successful students will be able to:
describe the role that a bug tracker plays in a FOSS project, describe the different types of issues stored in a bug tracker and their priorities, identify and track the status of a particular bug report in the gnome-music project, confirm the existence of a bug, in a given version of gnome-music, write a bug report. |
Background:
Directions:
Deliverables:
Assessment:
Comments:
Additional Information:
Knowledge Area/Knowledge Unit | |
Topic | |
Level of Difficulty | |
Estimated Time to Completion | |
Materials/Environment | |
Author | |
Source | |
License |
Suggestions for the Open Source Project:
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License