5-A-Day
8982
Comment: converted to 1.6 markup
|
8964
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
Line 86: | Line 86: |
5-a-day --add <bugnumbers>}}} For example: {{{5-a-day --add 123456 123457 123458 123459 123460 | 5-a-day --add <bugnumbers>}}} For example: {{{ 5-a-day --add 123456 123457 123458 123459 123460 |
What is 5-A-Day?
We, that means everybody, will do 5 bugs a day - every day. With only five bugs that everybody looks at every day, we will cover a lot of ground.
What you can do? That's up to you, your interests and your abilities.
- If you're a developer, you can help out reviewing patches and getting them uploaded.
- If you want to just confirm new bugs, you can do that.
- If you've experience with a certain package and want to triage bugs you can do that and forward them upstream if necessary.
- If you know your way around Ubuntu quite well, you can help assign bugs to the right package.
What you need to do to participate?
If you haven't helped out with bugs before you might want to take a look at Bugs/HowToTriage or ask the nice people on #ubuntu-bugs on irc.freenode.net.
Check out the section on Automatic Reporting to see how to participate.
See how you are doing over here: http://daniel.holba.ch/5-a-day-stats/
Print out the 5-a-day Playbook to hand out to participants. 5-a-day.pdf
Join the Launchpad team
Anybody who reports bugs
Did you report a bug on a previous release of Ubuntu?
- Is it the best quality bug report it could be?
- Could it use a better summary or a test case?
- Do you know if the bug is still occurs in the development release?
You can review the bugs you've reported at https://bugs.launchpad.net/people/+me/+reportedbugs .
Not a developer?
Once you feel comfortable to start triaging, the following lists may be a helpful starting point:
Bugs reported using the "Help -> Report a Problem" contain detailed information regarding the system the bug was reported on therefore they can be easier to triage. They are all tagged 'apport-bug' and you can find ones with a status of "New" at New apport-bugs.
Bug reports that were submitted yesterday and are still in a New status can be found at http://people.ubuntu.com/~brian/reports/yesterday/
- It is unfortunately the case that new bug reports will sometimes go unanswered. This is actively being addressed, but we can always use additional help. The following are lists of bug reports marked as "New" against older kernels.
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bugs?field.status=NEW
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bugs?field.status=NEW
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bugs?field.status=NEW
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bugs?field.status=NEW
- If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
- Additionaly, if the issue still exists, it would be useful to know if it is still present in the actively developed kernel.
- If you're interested on GUI applications you may want to take a look to:
Product
Debugging Instructions
Reviewing bugs marked for expiration - https://bugs.launchpad.net/ubuntu/+expirable-bugs
Bugs that need forwarding to the Upstream bugtrackers (Instructions)
You're a developer?
You might be interested in the following lists of bugs:
Reviewing patches: http://daniel.holba.ch/harvest/
- Make sure the bug is still relevant.
- Assign it to you.
Transform the patch into a debdiff if necessary.
- Make sure it builds and fixes the bug.
Add it to the sponsoring queue or upload it yourself.
- The Kernel:
http://people.ubuntu.com/~ogasawara/hardy-buglist.html - It's an excellent starting place for the community to get involved and work with the Ubuntu kernel team.
Automatic Reporting
This step is optional, but will automatically report your bug numbers and update your signature file if you like it to. Also http://daniel.holba.ch/5-a-day-stats/ generates statistics from that data.
Reporting to the 5-A-Day log
Add the following line to your /etc/apt/sources.list:
For Hardy:
deb http://ppa.launchpad.net/5-a-day/ubuntu hardy main
For Gutsy:
deb http://ppa.launchpad.net/5-a-day/ubuntu gutsy main deb http://ppa.launchpad.net/bughelper-dev/ubuntu gutsy main deb http://ppa.launchpad.net/bzr/ubuntu gutsy main
BRYou can also use the "Software Sources" Editor: BR attachment:apt-sources.png
Install the five-a-day package:
sudo apt-get update; sudo apt-get install five-a-day
Tell 5-a-day which Launchpad user you have:
echo <Your Launchpad ID> > ~/.5-a-day
- please note: this is not the email address you used for signing up for LP, but the last part of the URL that https://launchpad.net/people/+me redirects you to (everything behind the ~ sign). BR e.g. The user dholbach would type in:
echo dholbach > ~/.5-a-day
If you haven't done so, add your SSH key to Launchpad. If you don't have an SSH key, follow the instructions on this page to generate one. (Else 5-A-Day is not going to work.)
Run 5-a-day --add:
5-a-day --add <bugnumbers>
For example:
5-a-day --add 123456 123457 123458 123459 123460
Done. (Please note: you can also use the 5-A-Day applet - see below.)
Further notes:''
Run: and it will automatically update your signature. (It will also preserve an old ~/.signature file if it finds it.) Make sure your mail client picks up the shiny new ~/.signature.
Run:
Run Check out this video to see how it works.
We explicitly want LoCo teams to be in this. Sure the motu team would do great, the bugsquad too but that would be cheating, wouldn't it? Run for example: (Note: You need to member of that team.) check out your Launchpad team participation page. find the LoCo team you're member of
This new feature is particularly useful during events like Hug Days or Bug Jams. Make sure you have five-a-day version >= 0.26 installed. Run Run
If you're part of a LoCo Team, participate in 5-a-day for your team. Update ~/.signature
5-a-day --update
Generate a blog "signature"
5-a-day --update --html
and it will spit out HTML code you can add to your blog entry.5-A-Day Applet
sudo apt-get update; sudo apt-get install five-a-day-applet
Contribute within your LoCo Team
5-a-day --add-team <your LoCo Team's LP ID>
5-a-day --add-team ubuntu-berlin
Tagging 5-A-Day Bugs
5-a-day --add-tag tag-you-are-going-to-use
5-a-day --remove-tag tag-you-are-going-to-use
to stop using the particular tag.
5-A-Day (last edited 2016-10-27 07:46:00 by dholbach)