openSUSE:Bug Day
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 15.6. It’s of course okay to run openSUSE in a virtual machine.
- An IRC client or Matrix client to interact with the other participants
- You need an account on bugzilla.opensuse.org
- 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 https://meet.opensuse.org/meeting and people will be happy to help. You can also use our #openqa:opensuse.org matrix channel.
How to report issues
Our submitting bug reports manual should help you to make a perfect bug report. Please make sure that you review related Known bugs page before entering a new bug.
Our engineers will need logs and information about the system and installed software. Some of the teams even have specific information about what particular log files are they interested in.
March 7th: Leap 15.6 Beta
Why
Leap 15.6 just entered Beta. We have quite some changes including GNOME 45, and we'd like to know how Leap 15.6 works out for you.
Please do your usual workflows and help to improve Leap 15.6 quality by reporting any issues you find on the way.
When
The live Bug event will start at 9:00 CEST on March 7th, 2024.
Who
Anyone using openSUSE is welcome to help.
You need an account on bugzilla.opensuse.org
Where
We'll be using Known bugs 15.6 as a dashboard and a collaboration document.
Don't be afraid to edit it!
The live Bug Day event will replace our regular Thursday weekly meeting on 7th March and will be streamed to openSUSE channel at youtube.
Reward
You can expect that most of these issues will get fixed by the GA in early June 2024.
And you'll be happily able to use Leap 15.6!
Known 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. See our Buy Day archive for older records.
- openSUSE Leap 15.6:
- openSUSE Leap 15.5:
- openSUSE Leap 15.4:
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 2024-03-07 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 15.5):
- Set status to RESOLVED, FIXED.
- Add a comment like:
This has been fixed in Leap 15.5.
- If you have a strong feeling that the bug is fixed in recent versions:
- Set status to RESOLVED, NORESPONSE.
- Add a comment like:
15.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 15.5/15.6 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.