The wikis are now using the new authentication system.
If you did not migrate your account yet, visit https://idp-portal-info.suse.com/

openSUSE:Bug Squashing KDE

Ga naar: navigatie, zoeken

KDE Bug verslaan sessie

Het doel van de bug verslaan sessie is het verminderen van het aantal KDE bugrapporten op de Novell bugzilla. Er zijn nu venkele honderden bugrapporten toegekend aan KDE-onderhouders, hergeen een aantal is dat de mogelijkheden van het huidige KDE-team om ze te repareren (of zelfs te behandelen zonder er een grote hoeveelheid tijd op te verspillen). Een belangrijk aantal bugrapporten behoort tot de 'upstream bugzilla' volgens de richtlijnen voor upstream- vs downstream rapportagerichtlijnen, bovendien kunnen veel bugrapporten niet langer geldig zijn om verschillende reden (gerepareerd upstream inmiddels, geen antwoord van de indiener wanneer gevraagd om extra gegevens, etc.).

Dit artikel is nog maar gedeeltelijk vertaald. Als u mee wilt helpen met vertalen lees dan Wiki vertalen naar het Nederlands.

How to take a part

Please read guidelines for KDE bugreports screening before starting.

If you want to help, openSUSE:Bug_Squashing_KDE_bugreports has a list of assigned bugreport number ranges. Select one that is free (has ? next to it) and edit the page to assign it to yourself (add your name). When you are done with the range, mark it as DONE. If there are any bugreports that you cannot handle for any reason (you don't have the necessary hardware, you don't understand the problem, etc.), add the bugreport number to the appropriate list in openSUSE:Bug_Squashing_KDE_bugreports.

If you have any questions, feel free to ask in #opensuse-kde.

Tasks

There are several criteria which may be used for checking validity of a bugreport:

Checking old NEEDINFO bugreports

Check the query for bugreports which are in NEEDINFO state for longer than a month. See section 'Incomplete bugreports' in openSUSE:Bug Screening KDE#Reviewing_bugreports. Note that if the NEEDINFO is for another developer (somebody with Novell email), they should be pinged instead.

Checking whether old bugreports are still valid

Here are queries for openSUSE 11.0, openSUSE 11.1 and openSUSE 11.2. They should be checked with a recent KDE version (from openSUSE 11.3 or the KDE:Distro:Stable, KDE:Distro:Factory or KDE:KDE4:UNSTABLE repositories) whether they are still valid. If they are not valid, they should be closed as RESOLVED FIXED with a comment stating that in the new KDE version the bug is not present, unless the bug is very serious, enough to justify an online update (add such bugreports to the 'Online update' section in openSUSE:Bug_Squashing_KDE_bugreports). If the bugreport is still valid, add a comment stating in which KDE version the bug still exists and make sure the bug status is ASSIGNED.

Note that this applies to KDE3 bugreports too. As openSUSE 11.3 does not officially support KDE3, problems that exists only in KDE3 should be closed as RESOLVED WONTFIX with comment saying something like 'We no longer fix non-critical KDE3 problems.'. If a problem reported for KDE3 exists in KDE4 too, the component in the bugreport should be adjusted correspondingly.

Upstreaming bugreports

Note: This task requires already a little experience with handling of bugreports and is not recommended for new community members. Please try with other tasks first.

Here is a query for all P4 bugreports and P3 bugreports. According to the guidelines, all bugreport with priority less than P2 that are not openSUSE-specific should be forwarded to upstream bugzilla and closed as RESOLVED UPSTREAM.

If the bugreport itself already references an upstream bugreport, just close it. If not, you can try to find a possible upstream bugreport yourself. You can use the advanced search there (if there is a backtrace, search for the topmost entry in it, if there is an error message, try searching for the fixed part of it, etc.). This link will give you a table with all bugreports for components of a specific bugzilla product (edit the 'kwin' in the URL to whichever part of KDE is responsible). If you find such bugreport, add it to the URL field in bugzilla and close the bugreport with a comment like:

'Please next time report non-major problems that are not openSUSE-specific directly upstream at http://bugs.kde.org (http://en.opensuse.org/openSUSE:Bugreport_KDE#Report_at_bugzilla.novell.com_or_bugs.kde.org.3F)'

If you cannot find an upstream bugreport for the issue, you can either report it yourself (in which case then close the original one as said above), or you can ask the reporter to do that themselves (e.g. if they may be asked for further information by upstream developers, or even just if forwarding them upstream is too time consuming). Close then the bugreport with a comment like:

Please report your problem directly upstream at http://bugs.kde.org (http://en.opensuse.org/openSUSE:Bugreport_KDE#Report_at_bugzilla.novell.com_or_bugs.kde.org.3F)'.

See also section 'Decide whether the bugreport should be kept in Novell bugzilla or upstreamed' in openSUSE:Bug Screening KDE.

Handling P5 bugreports

Note: This task requires already a little experience with handling of bugreports and is not recommended for new community members. Please try with other tasks first.

This query lists all P5 bugreports that haven't been processed yet. They should be handled according to the guidelines at openSUSE:Bug Screening KDE.