This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]

openSUSE:Bug Day

Jump to: navigation, search
A bug day is a special day where a group of people focuses on triaging bugs in Bugzilla.

General Information

What is a Bug Day?

This is a day when many people from the community help to triage bugs in Bugzilla: during a full day, people come on IRC and help each other triage bugs. And for you it’s a very easy way to get involved in the openSUSE project!

Please note that this is only for openSUSE bugs living in our Bugzilla, but a solution for some bugs might be to forward them upstream.

How to participate

You usually only need the following to participate:

  • A recent version of openSUSE, like Tumbleweed, Leap 42.2 or 42.3. It’s of course okay to run openSUSE in a virtual machine.
  • An IRC client to interact with the other participants
  • Good mood :-)

If you know bug triage, just do it, else the organizers will give you a list of bugs that you can work on and you can double-check with other participants that your changes are okay.

On the announced day, simply join the #opensuse-bughunting channel on the freenode network and people will guide you!

August 10-12, 2017: focus on "zombie" bugs

For this specific Bug Day, we will focus on the “zombie” bug reports: those are reports against old versions of openSUSE (openSUSE 10-13, Leap 42.1). As some reports might still be valid, we don’t want to close all of them automatically. We will therefore check all those reports to see if they are still valid in the latest version of openSUSE (Leap 42.2 or 42.3). The goal is to close those bug reports if possible, or, if they are still valid, to move them to a current version of openSUSE so that they’re not lost in limbo.

So join us in the #opensuse-bughunting channel on the Freenode network! See this post on the opensuse-factory mailing list for more information.

Bug lists

Try to work on bugs for older versions first, but if you can't find any to handle, by all means do look at bugs for newer versions.

Example of possible resolutions

In general, it can be useful to always add in the comment the fact that you triaged the bug as part of the bug day. For example, you can append the following sentence to the end of the comment when submitting your change:

(changed during the 2017-08-10 bug day about bugs for obsolete versions of openSUSE)

  • If you know the bug has been fixed in a recent version of openSUSE (e.g. Leap 42.3):
    • Set status to RESOLVED, FIXED.
    • Add a comment like:

This has been fixed in Leap 42.3.

  • If you have a strong feeling that the bug is fixed in recent versions:
    • Set status to RESOLVED, NORESPONSE.
    • Add a comment like:

10.3 is obsolete now and there was not enough information for this bug to get fixed. I'll close this as NORESPONSE. If you can still reproduce it in Leap 42.2/42.3 or Tumbleweed, please reopen the bug and move it to the appropriate product. Thanks!

  • If you know the bug is not fixed, but it's clearly a change (feature or fix) that is not specific to openSUSE, you can forward the bug upstream:
    • Open a bug upstream, with a reference to the openSUSE bug.
    • Set status to RESOLVED, UPSTREAM.
    • Set URL to the URL of the upstream bug you opened.
    • Add a comment explaining that you sent the bug upstream.

See also

  • openSUSE:Open-Bugs-Day - like a Bug Day but on the development versions - this time until openSUSE 11.4 Release Candidate 1 (11.4 RC1) on the 2011-02-20