UbuntuBugDay
8657
Comment: Removed time bug urls as they didn't seem that useful / important
|
8669
Modified kernel team url
|
Deletions are marked like this. | Additions are marked like this. |
Line 96: | Line 96: |
* overview: https://launchpad.net/~kernel-bugs/+packagebugs | * overview: https://bugs.launchpad.net/~ubuntu-kernel-team/+packagebugs |
ContentsBRTableOfContents |
Announcing the Hug-for-a-bug Day
We've recently released the fifth milestone, or [http://www.ubuntu.com/testing/herd5 Herd 5], of the Feisty Fawn release. Now would be an excellent time to jump in and help with the testing.
We know where our success comes from. We're going to have lists of things to do for different Ubuntu teams, so we can better track the impact we had. Planning is one thing, but we'll surely stick to our concept of success: the Hug Day. This is a very special Bug Day: on Hug Day, when someone closes a bug, then someone else should hug him/her. Why? This is a very special way for us to tell everyone that we love contributions! And triaging bugs is a really big contribution.
In addition to that we added ["UbuntuBugDay/BugsForExtraPoints"] - a page where you can list your most annoying bugs. Fixing these bugs will give extra points and extra hugs of course.
Join the Hug Day
Who can join the Hug Day? Everyone. You don't need to be a developer. You don't need to know to code. Everyone is welcome. If you don't know how to help, then just come and we'll explain everything to you.
Where to join the Hug Day? #ubuntu-bugs on freenode [:IRC]. And you can go there every other day too!
When
Next Hug day is 7 March 2007, in all timezones. But again, you can go there every day and help with triaging the bug tracking systems.
We can't stress it enough: everyone can help. So join us for the Hug Day!
Main Objectives for the Hug Day
- Accepting people into [:UbuntuQA]
[http://tinyurl.com/rc4bs Unconfirmed bugs]
[https://wiki.ubuntu.com/Bugs/HowToTriage#head-ab0eb9d7731fa877b5fc866eedc4c312dab50ee7 Forward bugs upstream]
Everyday Tasks
Stuff to sink our teeth in.
- Forwarding bugs upstream
[http://tinyurl.com/rxjtk Bugs against Ubuntu].
- Post-release cleanup: there are bugs still opened on Malone that were fixed in Dapper. It is about time to have them closed.
- Laptop bugs:
[https://launchpad.net/ubuntu/+source/gnome-power-manager/+bugs gnome-power-manager]
[https://launchpad.net/ubuntu/+source/acpi-support/+bugs acpi-support]
[https://launchpad.net/ubuntu/+source/powernowd/+bugs powernowd]
[https://launchpad.net/ubuntu/+source/pbbuttonsd/+bugs pbbuttonsd]
[https://launchpad.net/ubuntu/+source/kdeutils/+bugs klaptopdaemon]
- Network related bugs:
- Desktop Team:
[https://launchpad.net/~desktop-bugs/+packagebugs Bug overview]
[https://wiki.ubuntu.com/DesktopTeam/Bugs Triaging Information]
- MOTU Science Team:
The [https://launchpad.net/~motuscience/ MOTU Science team] (["MOTU/Teams/Science"]) wants to get all the [https://launchpad.net/~motuscience/+packagebugs science related bugs] triaged and at least a few Hugs earned.
Ping LaserJock if you need something or have a question.
- KDE/Kubuntu Team:
[https://launchpad.net/~jr/+assignedbugs more bugs]
- Poke Riddell for help
- Firefox:
There are many [https://launchpad.net/ubuntu/+source/firefox/+bugs?field.searchtext=&orderby=-priority%2C-severity&advanced=1&field.assignee=&field.unassigned.used=&field.include_dupes.used=&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status-empty-marker=1&field.severity-empty-marker=1&field.attachmenttype-empty-marker=1&search=Search Unconfirmed firefox bugs] and any help triaging them would be greatly appreciated.
See DebuggingFirefox for some hints and tips.
- ["XSwat"]
[https://launchpad.net/~ubuntu-x-swat/+packagebugs package overview]
[http://tinyurl.com/9gs46 Unconfirmed Bugs]
[http://tinyurl.com/9zma4 Confirmed Bugs]
- talk to fabbione, infinity or rodarvus
Everything related to hotplugging ([https://launchpad.net/ubuntu/+source/hal/+bugs hal] and [https://launchpad.net/ubuntu/+source/gnome-volume-manager/+bugs gnome-volume-manager] bugs)
- This needs many testing especially on current Dapper. Many open bugs are probably fixed in current Dapper, and didn't see an updated test from the original reporter. Also, many are just not easy to reproduce.
- Talk to pitti on IRC.
- Security bugs
- Mark as "Security" via "Visibility/Security".
- For packages in "main" or "restricted", subscribe "ubuntu-security".
- For all other packages, subscribe "motu-swat".
For bugs that have a CVE number, attach it via "Link to CVE". The list of assigned CVE numbers are automatically tracked on [http://people.ubuntu.com/~pitti/ubuntu-cve ubuntu-cve], and are also listed at [http://cve.mitre.org/cve cve.mitre.org].
If you find a vulnerability without a CVE number, ask a member of the [https://launchpad.net/~ubuntu-security ubuntu-security team] about finding one, as these numbers are important for efficient tracking between upstream and other vendors.
- Screensaver bugs
Confirm and hunt [https://launchpad.net/ubuntu/+source/gnome-screensaver/+bugs gnome-screensaver bugs]
- Kernel Team:
- Crashers
[https://launchpad.net/ubuntu/+bugs?field.searchtext=apport&search=Search bugs probably reported by apport]
[https://launchpad.net/ubuntu/+bugs?field.searchtext=crash&search=Search crash]
[https://launchpad.net/ubuntu/+bugs?field.searchtext=segfault&search=Search segfault]
[https://launchpad.net/ubuntu/+bugs?field.searchtext=backtrace&search=Search backtrace]
Resources
["UbuntuBugDay/Attending"] (People from the Distro team attending)
["UbuntuBugDay/Draft"] (Draft of the announcement mail)
UbuntuBugDay (last edited 2014-07-09 19:30:52 by adsl-74-179-96-83)