Changes

358 bytes added ,  12:09, 19 March 2010
m
Line 63: Line 63:  
Now that you've finished writing your ticket, it's time to categorize it so that it gets to the right people when you file it. We'll walk through each of the important categorizations in turn.
 
Now that you've finished writing your ticket, it's time to categorize it so that it gets to the right people when you file it. We'll walk through each of the important categorizations in turn.
   −
There are two types of tickets: '''defects''' and '''enhancements.''' Defects are things you think are broken. If you can't get something to work, that's a defect. Enhancements are ideas on how to make something that ''isn't'' broken better - maybe you have an idea for a new feature that will let you do things that you can't do with the software right now.
+
The first section (highlighted in purple) is the ticket '''type.''' There are two types of tickets: '''defects''' and '''enhancements.''' Defects are things you think are broken. If you can't get something to work, that's a defect, and you should choose the "defect" option. Enhancements are ideas on how to make something that ''isn't'' broken better - maybe you have an idea for a new feature that will let you do things that you can't do with the software right now. If your ticket is an enhancement, choose the "enhancement" option.
   −
Tickets also specify '''components.''' This tells us which part of the software we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem.
+
The next sections we need to look at (highlighted in green) are the '''component''' and '''distribution/OS''' sections. Tickets specify '''components''' to tell us which part of the software we should look at, and who might want to look at it. For instance, if we were working on a bicycle, you might report a bug in the "handlebar" component - that way, we know to just look at the handlebar when we're fixing things, and the people who only want to work on tires know they don't have to worry about that problem. '''For [[Sugar on a Stick]], the component is ''SoaS''.'''
   −
Finally, there's the '''distribution.''' For [[Sugar on a Stick]], the distribution is [http://fedoraproject.org Fedora]. You can [http://en.wikipedia.org/wiki/Linux_distribution learn more about what Linux distributions are on Wikipedia], but this probably isn't the most important information to know - it's just extra information that can help developers figure out what's going on.
+
Finally, there's the '''distribution.''' '''For [[Sugar on a Stick]], the distribution is ''[http://fedoraproject.org Fedora]''.''' You can [http://en.wikipedia.org/wiki/Linux_distribution learn more about what Linux distributions are on Wikipedia], but this probably isn't the most important information to know - it's just extra information that can help developers figure out what's going on.
    
[[Image:Soas-bugfiling.png]]
 
[[Image:Soas-bugfiling.png]]
779

edits