* Arthur Pemberton [21/11/2008 17:02] :
>
> Wait, there is already an XML-RPC extension?

The XML-RPC work first appeared in Bugzilla 3.0:
http://www.bugzilla.org/releases/3.0/release-notes.html#v30_feat_xml

Bugzilla 3.2 final should be released at the end of the month and
extends the existing code considerably.

We'll give credit to everyone involved at release time but I want to
point that Red Hat's Bugzilla team contributed heavily to Bugzilla's
XML-RPC codebase, submitting their modifications back to upstream,
helping with QA, ...

> My (possible) time may be
> better spent building a UI then?

Probably.
We'ld like to have more users of the Bugzilla XML-RPC methods, so that
we can extend the code in ways the users wish them.
Please don't hesitate to join us on irc or our mailing lists if you need
help building on Bugzilla or if you want to talk about it.

Emmanuel

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

* Les Mikesell [21/11/2008 20:49] :
>
>> Deciding to push a bug upstream or not cannot be reduced to checking a
>> box or pushing a button.
>
> Wrong answer, if anyone actually wants those bug reports.

Sheer volume of bug reports will not improve development, especially
if the increase is only in the form of duplicate bugs. In fact, this
will slow down development because more time will have to be spent on
bug triage, taking time away from bug fixing.

Emmanuel

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Nov 21, 2008 at 11:36 AM, Emmanuel Seyman <emmanuel.seyman@club-
> Sheer volume of bug reports will not improve development, especially
> if the increase is only in the form of duplicate bugs. In fact, this
> will slow down development because more time will have to be spent on
> bug triage, taking time away from bug fixing.


There really is no way of getting around the fact that for a lot of
bugs (other than crash reports like kerneloops) triage by an actual
human being may be the pacing item. If we were going to make a
concerted effort to bring more people in to do triage can we stand up
a target? Do we know how many new bugs we have filed in a typical
week? Can we make a statement that we'd like to see individual
triagers triage X number of bugs in a day or a week on average? Can
we those sort of numbers to put a target together for a triage
recruitment push? How many people do we need triaging for our current
bug ticket churn rate right now?

-jef

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Nov 21, 2008 at 11:58:56PM +0100, Matej Cepl wrote:
> On 2008-11-21, 11:25 GMT, Emmanuel Seyman wrote:
> > Thanks for making their work more difficult, I guess.
>
> I am a bugmaster for the desktop team, so I know a little bit
> what I am doing -- if you are sitting on the email getting all
> NEW bugs into your desktop, catching duplicates is not that big
> problem. After some time, you have some handle on what's the
> current bug-of-the-week, which helps you to quickly eliminate
> many bugs just in the beginning.

How does one sign up to get all NEW bugs for a certain component?

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Nov 21, 2008 at 5:26 PM, Chuck Anderson <cra@wpi.edu> wrote:
> On Fri, Nov 21, 2008 at 11:58:56PM +0100, Matej Cepl wrote:
>> On 2008-11-21, 11:25 GMT, Emmanuel Seyman wrote:
>> > Thanks for making their work more difficult, I guess.
>>
>> I am a bugmaster for the desktop team, so I know a little bit
>> what I am doing -- if you are sitting on the email getting all
>> NEW bugs into your desktop, catching duplicates is not that big
>> problem. After some time, you have some handle on what's the
>> current bug-of-the-week, which helps you to quickly eliminate
>> many bugs just in the beginning.
>
> How does one sign up to get all NEW bugs for a certain component?

Depends on what you want, if you just want a list to look at, I have
found creating a live bookmark with the rss feed or using google rss
tools to be very helpful.
For instance this would give you the bugs that are in state NEW or
ASSIGNED for component anaconda in fedora 9 and rawhide. I still have
not been able to use the query to order the bugs by date, as I recall
this is done with some cookie magic.

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&cla ssification=Fedora&component=anaconda&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=version&field-1-4-0=bug_status&product=Fedora&query_format=advanced& remaction=&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=anyexact&value-1-0-0=Fedora&value-1-1-0=Fedora&value-1-2-0=anaconda&value-1-3-0=9%2Crawhide&value-1-4-0=NEW%2CASSIGNED&version=9&version=rawhide&title=B ug%20List&ctype=atom

otherwise I think you have to be in the group for that component,
others know more about this then I do.

--Brennan Ashton

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Nov 21, 2008 at 4:00 PM, Les Mikesell <lesmikesell@gmail.com> wrote:
> Matej Cepl wrote:
>>
>> On 2008-11-21, 20:53 GMT, Les Mikesell wrote:
>>>
>>> That's something that less specialized volunteers could do.
>>
>> Yes, but there is severe lack of them -- it is not that sexy as hacking on
>> kernel, I suppose.
>
> If it were as easy as moderating a mailman list there might be more takers.
> What's the current workflow and where have you requested volunteer help?

Where we are really in need of more volunteers is in BugTriage,
especially after the start of the new year. What people need to do to
help is documented on the BugZappers section of the wiki
https://fedoraproject.org/wiki/BugZappers while I would much rather
then hacking away on the kernel as I did for a while on a different
project, this is in some ways just as important.

--Brennan Ashton

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list