Mailinglist Archive: opensuse-project (229 mails)
| < Previous | Next > |
Re: [opensuse-project] Zombie bugzilla entries
- From: Marcus Meissner <meissner@xxxxxxx>
- Date: Sun, 14 Nov 2010 11:43:10 +0100
- Message-id: <20101114104309.GA26320@xxxxxxx>
On Sun, Nov 14, 2010 at 11:22:03AM +0100, Kálmán Kéménczy wrote:
qa@xxxxxxx really is a virtual team... Consisting of 0 (zero) people
for openSUSE in Bugzilla context.
There is some community testing team led by Holgi as far as I know, but
I am not sure it takes care of reviewing bugzilla entries.
The bnc-team-screening team are 1 or 2 chinese QA engineers that assign
bugs away from the screening address to the maintainers.
Ciao, Marcus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
Many of bugs I reported ended up in this state. Examples are broken
intel graphics since 11.3 (but I'm at least reminded to test the latest
release every 2 months or so), reported bug in nmap with exact line
number and described error. The same for libacl. Vim parses the gcc
output wrong since we use gcc 4.5 and many others. The last four are
fixable in an hour, but the assigned people don't care for years. I'm
not counting gnome bugs which are assigned for years to gnome screening
team and are not touched at all by anybody.
In that case QA should step in! every bug has a QA member, we have to
ask them ehat is the problem, how can we help to move forward, should
we change some process or what is their opinion?
qa@xxxxxxx really is a virtual team... Consisting of 0 (zero) people
for openSUSE in Bugzilla context.
There is some community testing team led by Holgi as far as I know, but
I am not sure it takes care of reviewing bugzilla entries.
The bnc-team-screening team are 1 or 2 chinese QA engineers that assign
bugs away from the screening address to the maintainers.
Ciao, Marcus
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |