2009 Q3 Report

[Andre Klapper]

Heja bugsquadders,

last quarter we started to have status reports by GNOME teams. See
http://foundation.gnome.org/reports/gnome-report-2009-Q2.pdf for the
last one.

Stormy has now asked to provide a Bugsquad report for Q3 (July-September
2009) by Friday, October 9th.

Anybody volunteering (as I'm short in time next week)?

andre
--
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Andre Klapper]

Am Freitag, den 02.10.2009, 22:02 +0200 schrieb Andre Klapper:

> Heja bugsquadders,
>
> last quarter we started to have status reports by GNOME teams. See
> http://foundation.gnome.org/reports/gnome-report-2009-Q2.pdf for the
> last one.
>
> Stormy has now asked to provide a Bugsquad report for Q3 (July-September
> 2009) by Friday, October 9th.
>
> Anybody volunteering (as I'm short in time next week)?

Quick initial version. Please feel free to change/enhance:



In August GNOME Bugzilla was updated to version 3.4 by Max-Kanat
Alexander with huge help of Olav Vitters and Owen Taylor. The previous
version was several years old and did not receive any upstream security
fixes anymore. It also had several GNOME-only enhancements that
partially have been ported to 3.4 though some regressions remained.
The server hardware was also improved so timeout issues when running
complex queries do not happen anymore.

TODO: Is there a way to find out the top bug closers of the last 3
months?

9227 reports (bugs + feature requests) were opened* and 8751 were
closed**.

The GNOME Bugsquad has started to have monthly meetings to discuss
policies and issues. The new policy to handle old forgotten reports is
in place and has been revised after feedback from developers.


* https://bugzilla.gnome.org/buglist.cgi?chfieldto=-3d;query_format=advanced;chfield=[Bug%20creation];chfieldfrom=-94d;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;bug_status=RESOLVED;bug_status=VERIFIED
** https://bugzilla.gnome.org/buglist.cgi?chfieldto=-3d&chfield=bug_status&chfieldfrom=-94d&chfieldvalue=RESOLVED&bug_status=RESOLVED&bug_status=VERIFIED

-andre
--
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Javier Jardón]

Hey Andre,

2009/10/3 Andre Klapper <ak-47@...>:

>
> Quick initial version. Please feel free to change/enhance:
>
> In August GNOME Bugzilla was updated to version 3.4 by Max-Kanat
> Alexander with huge help of Olav Vitters and Owen Taylor. The previous
> version was several years old and did not receive any upstream security
> fixes anymore. It also had several GNOME-only enhancements that
> partially have been ported to 3.4 though some regressions remained.
> The server hardware was also improved so timeout issues when running
> complex queries do not happen anymore.
>
> TODO: Is there a way to find out the top bug closers of the last 3
> months?
>
> 9227 reports (bugs + feature requests) were opened* and 8751 were
> closed**.
>
> The GNOME Bugsquad has started to have monthly meetings to discuss
> policies and issues. The new policy to handle old forgotten reports is
> in place and has been revised after feedback from developers.

I think a link to the meeting page would be good: [1]

How about speak about the new policy changes? Something like this
(from your blog post):

"- Bug reports in GNOME Bugzilla (not enhancement requests an in
UNCONFIRMED status) with 1 year without any activity will be set to
NEEDINFO state and reporters will be asked to update the report’s
status by testing again on a recent GNOME version. A new stock answer
will be made available for this [2]
- All NEEDINFO bugs without a response after 6 weeks will be closed as
RESOLVED INCOMPLETE.
- The “FIXED” stock answers will kindly ask bug reporters to verify
the fix once it has landed in their distribution and if they have some
time. The specific stock answers will be updated accordingly [3]."

Also, I think mention the work to clean bugzilla of
obsolete/unmaintained modules would be good too: (from you blog post,
again):

"There are many modules in GNOME Bugzilla that have not seen any code
changes for years (except for translation updates). Bugsquad members
will try to identify those obsolete/unmaintained modules and contact
the maintainers. We expect a response within four weeks from the
maintainers. Without a response the remaining reports will probably be
closed as WONTFIX while explaining to the reporter that the module is
not maintained anymore and will not receive any updates. You can track
work already done here: [5]"

And something new: we have our own module to keep track of assigned tasks [4]

Hope helps,

[1] http://live.gnome.org/Bugsquad/Meetings
[2] http://bugzilla.gnome.org/show_bug.cgi?id=591222
[3] http://bugzilla.gnome.org/show_bug.cgi?id=590840
[4] https://bugzilla.gnome.org/show_bug.cgi?id=594245
[5] http://live.gnome.org/Bugsquad/DeprecatedModules

--
Javier Jardón Cabezas
_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Olav Vitters]

On Sat, Oct 03, 2009 at 09:22:33PM +0200, Andre Klapper wrote:
> TODO: Is there a way to find out the top bug closers of the last 3
> months?

New functionality by Frederic Peters:

https://bugzilla.gnome.org/page.cgi?id=weekly-bug-summary.html
This has the day limitation thing like before.

https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=alexander@...


Both reports should accept the same arguments as before. They're
extensions, so should make it easier (not totally easy) for other
Bugzilla instances to use it. Sometimes it relies on GNOME Bugzilla
functionality though, those things can be fixed (hidden).

--
Regards,
Olav
_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Andre Klapper]

Am Dienstag, den 06.10.2009, 04:51 +0200 schrieb Javier Jardón:
> How about speak about the new policy changes?

Willing to come up with a version? It's not yet too late I'd say as
we're waiting for other teams.

andre
--
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Andre Klapper]

> Am Dienstag, den 06.10.2009, 04:51 +0200 schrieb Javier Jardón:
> > How about speak about the new policy changes?

Good idea, done.
Updated version attached as Stormy wrote today that the deadline is
Friday 16th (today in my timezone).

andre
--
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

In August GNOME Bugzilla was updated to version 3.4 by Max-Kanat Alexander with huge help of Olav Vitters and Owen Taylor. The previous version was several years old and did not receive any upstream security fixes anymore. It also had several GNOME-only enhancements that partially have been ported to 3.4 though some regressions remained.
The server hardware was also improved so timeout issues when running complex queries do not happen anymore.

From July to September, 9227 reports (bugs + feature requests) were opened and 8751 were closed.
Top bug closers were Akhil Laddha (484 reports), Fabio Durán Verdugo (455), Andre Klapper (269), Bastien Nocera (261) and Matthew Barnes (251).
Top bug reporters were Pedro Villavicencio (136 reports), Owen Taylor (116), Bastien Nocera (99), Colin Walters (92) and Matthias Clasen (87).

The GNOME Bugsquad has started to have monthly meetings to discuss policies and issues. The new policy to handle old forgotten reports is
in place and has been revised after feedback from developers.
UNCONFIRMED bug reports (but not enhancement requests) with one year without any activity will be set to NEEDINFO state and reporters will be asked to update the report’s status by testing again on a recent GNOME version.

When reports are closed as "FIXED" reporters will now kindly be asked to verify the fix once it has landed in their distribution and if they have some time.

As there are many modules in GNOME Bugzilla that have not seen any code changes for years (except for translation updates) the Bugsquad has started trying to identify those obsolete/unmaintained modules and contact the maintainers. Without a response the remaining reports will probably be closed as WONTFIX while explaining to the reporter that the module is not maintained anymore and will not receive any updates.

In order to improve workflow the Bugsquad now also has its own module in GNOME Bugzilla to keep track of assigned tasks.


_______________________________________________
gnome-bugsquad mailing list
gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad