=== SquishyNotHere is now known as squishy | ||
qwebirc92152 | . | 02:59 |
---|---|---|
=== leagris is now known as virtuald | ||
=== thisfred_ is now known as thisfred | ||
Ayrton | today is the class about bug triage? | 16:07 |
devildante | Ayrton: yes | 16:07 |
devildante | Ayrton: please chat in #ubuntu-classroom-chat instead ;) | 16:07 |
Ayrton | sorry, I forget about that | 16:08 |
devildante | Ayrton: np ;) | 16:08 |
hggdh | devildante: I will be around, if needed | 16:15 |
devildante | hggdh: thanks :) | 16:15 |
hggdh | devildante: my pleasure, and thank you for the class | 16:16 |
devildante | heh | 16:16 |
=== AndrewMC is now known as SpockVulcan | ||
=== SpockVulcan is now known as AndrewMC | ||
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Basics of Bug Triaging - Instructors: devildante | ||
ClassBot | Logs for this session will be available at http://irclogs.ubuntu.com/2010/12/15/%23ubuntu-classroom.html following the conclusion of the session. | 17:01 |
devildante | Hello everyone :) | 17:01 |
c2tarun | hello o/ | 17:01 |
devildante | I am Mohamed Amine IL Idrissi, and I will be your instructor for this session | 17:02 |
devildante | we'll talk about how we can help the Ubuntu community by triaging bugs | 17:03 |
devildante | okay let's begin | 17:03 |
devildante | First of all, what's bug triaging? | 17:03 |
devildante | The word may sound mysterious to you, but it's simple | 17:03 |
devildante | bug triaging means "preparing" a bug and making it ready for developers to fix it | 17:04 |
devildante | bug triaging requires no programming experience | 17:04 |
devildante | so it's a good way to delve into the Ubuntu community :) | 17:05 |
devildante | Open source/FOSS projects use various bug trackers | 17:05 |
devildante | Ubuntu uses Launchpad, a Canonical-developed platform | 17:06 |
devildante | that's what we will use to triage bugs | 17:06 |
devildante | any questions? | 17:06 |
c2tarun | what are bug trackers? | 17:06 |
devildante | c2tarun: ah yes, thanks for bringing this | 17:07 |
devildante | c2tarun: in a nutshell, bug trackers are places where you can report bugs, aka bring them to the attention of the developers | 17:08 |
devildante | c2tarun: for example, bugzilla is a bug tracker that is used by GNOME, Wine, etc... | 17:08 |
c2tarun | ok | 17:09 |
devildante | let's continue then | 17:09 |
devildante | like I said, Ubuntu uses Launchpad | 17:09 |
devildante | Launchpad provides a bug tracker that is simple to use | 17:10 |
devildante | but you may get a little confused | 17:10 |
devildante | so let's check a bug's life cycle | 17:10 |
devildante | first, the user reports a bug | 17:11 |
devildante | it can be done either via the "ubuntu-bug" command, or manually | 17:11 |
devildante | it's described here: https://help.ubuntu.com/community/ReportingBugs | 17:11 |
devildante | bug triagers, the persons who do the job of triaging, look at the bug then | 17:12 |
devildante | What's the nature of the bug? Is it well described? Can it be reproduced? and many other questions fly in the head of the triager | 17:13 |
devildante | If he sees that the bug has incomplete information, he marks it as Incomplete | 17:14 |
devildante | and that's where we introduces Statuses | 17:14 |
devildante | Statuses are a way to describe a bug: is it reproducible, etc... | 17:15 |
devildante | All newly reported bugs are marked initially as New | 17:15 |
devildante | Bugs with incomplete information are marked as Incomplete | 17:15 |
c2tarun | devildante: how can we come to know that the information provided is sufficient for developer? | 17:15 |
devildante | c2tarun: it depends | 17:16 |
devildante | c2tarun: if you report your bug via "ubuntu-bug", additional system information is added to it | 17:16 |
devildante | c2tarun: the bug must also be reproducible by someone else than the reporter | 17:17 |
c2tarun | ok | 17:17 |
devildante | for an example of an incomplete bug, see: https://bugs.launchpad.net/ubuntu/+source/imagination/+bug/627921 | 17:17 |
ubot2 | Launchpad bug 627921 in imagination (Ubuntu) "package imagination-common 2.1-1ubuntu1 failed to install/upgrade: intentando sobreescribir «/usr/share/doc/imagination/html/en/images/imagination_window.png», que está también en el paquete imagination 0:2.1-1 (affects: 3) (dups: 2) (heat: 35)" [Undecided,Incomplete] | 17:17 |
devildante | You see here that the bug is marked as Incomplete because the reporter upgraded a package from a version that was never in Ubuntu | 17:18 |
devildante | The triager asks him to fill in more details about that, and then marks the bug as Incomplete | 17:19 |
devildante | There are statuses other than New and Incomplete | 17:19 |
devildante | "Confirmed" means that the bug was able to be reproduced by someone other than the reporter of the bug | 17:20 |
devildante | example: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/690650 | 17:21 |
ubot2 | Launchpad bug 690650 in evince (Ubuntu) "Evince does not remember settings (affects: 1) (heat: 6)" [Undecided,Confirmed] | 17:21 |
devildante | we see here that the triager has been able to reproduce the bug | 17:21 |
devildante | thus, he marked it as Confirmed | 17:22 |
devildante | any questions until now? | 17:22 |
ElPasmo | Anyone can change the status to confirmed or only trusted members? | 17:22 |
devildante | Elpasmo: anyone | 17:23 |
c2tarun | most of the times there are no directions to reproduce the bug? how can we reproduce then? | 17:24 |
devildante | Statuses that are reserved to "trusted members" (the Ubuntu Bug Control team) are Triaged and Won't Fix | 17:24 |
devildante | c2tarun: if we can't reproduce the bug, we mark the bug as "Incomplete" and kindly ask the reporter to include steps to reproduce the bug | 17:25 |
c2tarun | asking reporter means just requesting in comments? | 17:25 |
devildante | yes | 17:25 |
c2tarun | OK | 17:26 |
ClassBot | wolffu asked: So if we are unable to reproduce the bug on our system, is there any reason to continue triaging? | 17:26 |
devildante | wolffu: we can't continue to triage a bug if we can't reproduce it | 17:27 |
devildante | wolffu: like I said, mark the bug as Incomplete and ask the reported to include steps | 17:27 |
devildante | okay let's continue | 17:28 |
devildante | "Triaged" means the bug has been, well, triaged :p | 17:29 |
devildante | it is then ready for a developer to fix | 17:29 |
devildante | not anybody can mark a bug as Triaged | 17:29 |
devildante | only Ubuntu Bug Control members | 17:30 |
devildante | if you see that a bug has complete information, ask at #ubuntu-bugs on IRC to triage the bug | 17:30 |
devildante | they are very kind :) | 17:30 |
devildante | but don't forget | 17:31 |
devildante | the bug must be complete | 17:31 |
devildante | that includes deciding which importance the bug will get | 17:31 |
devildante | Importance is how much the bug is "dangerous" or "annoying" | 17:31 |
devildante | it's better explained here: https://wiki.ubuntu.com/Bugs/Importance | 17:32 |
devildante | example here: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/685473 | 17:33 |
ubot2 | Launchpad bug 685473 in software-center (Ubuntu) "Multiple screenshots in software description (affects: 2) (heat: 312)" [Wishlist,Confirmed] | 17:33 |
devildante | the bug has been confirmed and marked as wishlist | 17:33 |
devildante | because it defines a feature request | 17:33 |
devildante | small feature requests are generally accepted in Launchpad | 17:34 |
devildante | but for big features, it's better to put it in http://brainstorm.ubuntu.com | 17:34 |
devildante | any questions up until now? | 17:35 |
devildante | okay let's continue | 17:36 |
devildante | one of the other criteria for a bug to be triaged is to be reported upstream | 17:37 |
devildante | what is upstream, you say? it is the projects that are above us, that we incorporate into the distribution | 17:38 |
devildante | downstream is the opposite of that | 17:38 |
devildante | for example, GNOME is upstream of all the gnome packages in Ubuntu | 17:38 |
devildante | and we are downstream of GNOME | 17:39 |
devildante | an example of an upstream reported bug: https://bugs.launchpad.net/ubuntu/+source/tasque/+bug/550990 | 17:39 |
ubot2 | Launchpad bug 550990 in tasque (Ubuntu) (and 1 other project) "Remember The Milk tasks should be synchronized for offline access (affects: 5) (heat: 24)" [Undecided,Triaged] | 17:39 |
devildante | as you see, there is now a second line above the ubuntu package line | 17:40 |
devildante | it represents the upstream bug | 17:40 |
devildante | there is a link in that line leading to the upstream bug | 17:41 |
c2tarun | what do you mean by upstream bug? | 17:42 |
devildante | c2tarun: upstream bug means it has been reported as a bug in the upstream bug tracker | 17:42 |
c2tarun | ok | 17:43 |
devildante | to link a bug to an upstream one, you first have to check if it exists in the upstream bug tracker | 17:44 |
devildante | if not, report a new one there, then link it back to upstream | 17:44 |
devildante | instructions for linking bugs to GNOME ones: https://wiki.ubuntu.com/Bugs/Upstream/GNOME | 17:45 |
devildante | questions? we still have time | 17:46 |
ClassBot | callaghan asked: How do Triagers get informed of newly submitted bugs? | 17:46 |
devildante | callaghan: very good question | 17:46 |
devildante | callaghan: you can check untriaged bugs here: http://goo.gl/25EjA | 17:48 |
devildante | you can also check them via an atom feed: http://feeds.launchpad.net/ubuntu/latest-bugs.atom | 17:48 |
devildante | or you can join the #ubuntu-bugs-announce channel on IRC | 17:48 |
devildante | finally, you can also subscribe to this mailing list: https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs | 17:49 |
c2tarun | how can we make into ubuntu bug control team? | 17:49 |
devildante | attention, it's very high volume | 17:49 |
devildante | c2tarun: triage bugs, triage bugs, and triage more bugs ;) | 17:49 |
c2tarun | :) | 17:49 |
devildante | c2tarun: when you're ready, follow instructions at https://launchpad.net/~ubuntu-bugcontrol/ to apply | 17:50 |
devildante | any other questions? | 17:50 |
ClassBot | There are 10 minutes remaining in the current session. | 17:51 |
devildante | okay, let's finish this | 17:51 |
c2tarun | on https://launchpad.net/~ubuntu-bugcontrol/ its mentioned about an application, what is it? | 17:51 |
devildante | c2tarun: it means that you should present yourself and your skills | 17:53 |
devildante | c2tarun: please follow instructions at: http://wiki.ubuntu.com/UbuntuBugControl | 17:53 |
ClassBot | callaghan asked: Do you need to subscribe yourself to a bug before triaging it? | 17:53 |
devildante | callaghan: no, not required | 17:54 |
callaghan | So I get updates on a bug as soon as I change something there? | 17:54 |
devildante | callaghan: also no | 17:54 |
devildante | callaghan: you need to be subscribed for that | 17:54 |
callaghan | ok, thank you :) | 17:55 |
devildante | callaghan: but to triage a bug, it's not required | 17:55 |
devildante | callaghan: but it's preferred | 17:55 |
devildante | callaghan: np ;) | 17:55 |
devildante | okay, let's put some finishing words :p | 17:55 |
devildante | what you just saw are the basics | 17:55 |
devildante | bug triaging can be more complex than that | 17:55 |
ClassBot | There are 5 minutes remaining in the current session. | 17:56 |
devildante | for example: https://bugs.launchpad.net/ubuntu/+bug/11334 | 17:56 |
ubot2 | Launchpad bug 11334 in ubuntu (and 16 other projects) "MASTER Copy-Paste doesn't work if the source is closed before the paste (affects: 262) (dups: 26) (heat: 1245)" [Wishlist,Confirmed] | 17:56 |
ClassBot | ElPasmo asked: What happens if there is some ways differents for solving a bug. Who decides? Example: bug 689655 | 17:57 |
ubot2 | Launchpad bug 689655 in main-menu (Ubuntu) (and 2 other projects) "application > accessories > take screenshot (should be take a screenshot) (affects: 2) (heat: 14)" [Undecided,Confirmed] https://launchpad.net/bugs/689655 | 17:57 |
devildante | ElPasmo: we just decide of the appropriate way in the comments ;) | 17:57 |
devildante | any other questions? we are close from the end of the session | 17:58 |
ClassBot | Logs for this session will be available at http://irclogs.ubuntu.com/2010/12/15/%23ubuntu-classroom.html | 18:01 |
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || | ||
devildante | okay thanks everyone, and bye :) | 18:01 |
c2tarun | Thanks :) | 18:01 |
callaghan | thx, bye | 18:01 |
devildante | callaghan: np | 18:01 |
devildante | c2tarun: np too :) | 18:01 |
ElPasmo | Thanks devildante :) | 18:02 |
devildante | ElPasmo: np :) | 18:03 |
qwebirc3958 | Woops. I missed class didn't I? | 18:23 |
UndiFineD | qwebirc3958, go get a note at the rectors office :P | 18:24 |
qwebirc3958 | Haha. Where are the logs for this channel kept, so I can see what I missed? | 18:24 |
qwebirc3958 | Nevermind. | 18:25 |
qwebirc3958 | Found em. | 18:25 |
qwebirc3958 | Informative session. Cya all. | 18:29 |
=== freddy is now known as Guest23349 | ||
=== kdrsx is now known as kuadrosx |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!