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 [:5-A-Day#Log:Automatic Reporting] to see how to participate.

• See how you are doing over here: http://daniel.holba.ch/5-a-day-stats/

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 you 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 sytem 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 [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=apport-bug&field.tags_combinator=ANY&field.has_no_package.used=&search=Search New apport-bugs].

• 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

    1. If the report has not had any recent activity, it would be helpful to know if the issue reported still exists or not.
    2. 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
    [https://bugs.launchpad.net/ubuntu/+source/update-manager/+bugs?field.status=NEW UpdateManager]	DebuggingUpdateManager
    [https://bugs.launchpad.net/ubuntu/+source/compiz/+bugs?field.status=NEW Compiz]	DebuggingCompiz

• Reviewing bugs marked for expiration - https://bugs.launchpad.net/ubuntu/+expirable-bugs

You're a developer?

You might be interested in the following lists of bugs:

• Reviewing patches:

  • https://lists.ubuntu.com/archives/ubuntu-devel/2008-January/024960.html explains how to get a list of bugs that have patches attached that did not make it to the sponsoring queue yet.

  • https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream is a list of bugs that were fixed Upstream or in other Distributions but not fixed in Ubuntu.

  • Make sure the bug is still relevant.
  • Assign it to you.

  • Transform the patch into a [:PackagingGuide/Recipes/Debdiff:debdiff] if necessary.

  • Make sure it builds and fixes the bug.

  • Add it to the [:SponsorshipProcess: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.

What you can do to spread the message?

• Add your 5 a day to your blog posts.

  • Either on http://planet.ubuntu.com ([:PlanetUbuntu] if you're part of ubuntumembers)

  • or on http://ubuntuweblogs.org/ (follow the [http://ubuntuweblogs.org/submit.html instructions])

• Add your 5 a day to mailing list posts (in the signature).

Example:

My 5 today:
 - Bug 123456 (upstream fix included in Ubuntu)
 - Bug 123457 (upstream fix included in Ubuntu)
 - Bug 123458 (explained about debdiff process)
 - Bug 123459 (sponsored the upload)
 - Bug 123460 (guided patch into sponsoring queue)

Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day

Anchor(Log)

Automatic Reporting

This step is optional, but will automatically report your [https://code.launchpad.net/~5-a-day/5-a-day-data/main bug numbers] and update your signature file if you like it to.

Reporting to the 5-A-Day log

1. 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

2. Install the five-a-day package:

   sudo apt-get update; sudo apt-get install five-a-day

3. Join the [https://launchpad.net/~5-a-day/+join 5-a-day] team on Launchpad.

4. Tell add-5-a-day which Launchpad user you have:

   echo <Your Launchpad ID> > ~/.5-a-day

5. If you haven't done so, add your [https://launchpad.net/people/+me/+editsshkeys SSH key to Launchpad].

6. Run add-5-a-day:

   add-5-a-day 123456 123457 123458 123459 123460

7. Done.

Update ~/.signature

1. Follow the steps above.

2. Run:

   update-signature

   and it will automatically update your signature. (It will also preserve an old ~/.signature file if it finds it.)

3. Make sure your mail client picks up the shiny new ~/.signature.

Generate a blog "signature"

1. Follow the steps above.

2. Run:

   update-signature --html

   and it will spit out HTML code you can add to your blog entry.

CategoryBugSquad