On Wednesday 24 May 2006 17:04, Marcus Meissner wrote:

On Wed, May 24, 2006 at 04:57:55PM +0300, Andras Mantia wrote:

...

Hi,

Can someone from SUSE tell me how bug handling is done there? I mean, if there is a bug reported for some version and is not fixed in that version, is it taken in account for upcoming versions or it is just forgotten? An example: - a bug (like #176249 and previously #148638) is reported for 10.0 - it was closed with WONTFIX as the change cannot be made to a released product

Should not have happened. In this case the bug should be assigned to the next product.

...

- the bug is still present in 10.1 (somebody reports again) - the bug is closed again as "it's too late and risky to do it"

Same as above.

I reopened in both cases. ;-)

You can reassign it to the next product, right now if possible.

If it is still in the codebase, say so, reopen it, move it to the next product.

Well, I cannot test the upcoming 10.2, so I cannot just reassign. ;-) But I make sure at least to keep the bugs open as still as it is present in versions that I test. Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org

Hi, and yet another Bug-handling related question: What happens if a report gets lost in NEEDINFO status even though the requested information was indeed provided. I.e., a bug is NEEDINFO'd to the reporter, the reporter provides the information but forgets to reset the NEEDINFO status. If a person without any relation to the bug notices that, is this person allowed to "step in" and reset the NEEDINFO status? Andreas Hanke

Hello, Am Mittwoch, 31. Mai 2006 11:55 schrieb Andreas Jaeger:

Andreas Hanke writes:

...

What happens if a report gets lost in NEEDINFO status even though the requested information was indeed provided. [...] If a person without any relation to the bug notices that, is this person allowed to "step in" and reset the NEEDINFO status?

Yes, everybody is allowed to change that, so go ahead if you find one,

Well, more or less... http://en.opensuse.org/Bug_Reporting_FAQ basically asks for resetting needinfo, but also contains the following paragraph: ----------------------------------------------------------------------- Please note that bugs which are assigned to the BNC-Screening-Team (mainly YaST- and X11-related problems) initially or during the process should not be set from NEEDINFO to ASSIGNED by the reporter or the person the information was requested from. This is because a change of this status almost always involves a reassignment which is done by this team. Changing this status might cause the specific bug to appear on the wrong listing and might therefore be not handled (reassigned) efficiently. Thank you for taking this into account. ----------------------------------------------------------------------- Sorry, but this is not very user-friendly and confusing (some assignees want needinfo reset, others won't). The result will probably be that people won't reset needinfo for other assignees because their first bugzilla contact often is the screening team :-( Other people (like me) will always reset needinfo (without checking the assignee ;-) after providing the requested information and never noticed that the screening team overlooked one of my bugs. Summary: I don't understand why the screening team prefers bugs to be kept in needinfo state - maybe you should ask them if this is really a good idea... Regards, Christian Boltz -- In its default setup, Windows XP on the Internet amounts to a car parked in a bad part of town, with the doors unlocked, the key in the ignition and a Post-It note on the dashboard saying, "Please don't steal this". [Washington Post, 23.8.2003] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory-help@opensuse.org