FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 04-05-2008, 12:41 AM
Chris Adams
 
Default Reverse bug triage

How about a triage process that pokes maintainers? I have a few bugs
that appear to be ignored by maintainers, despite all the necessary
information being provided:

- radiusclient-ng - BZ 236350
Nothing happened for over 9 months, then I supplied the one-line fix
(to the Fedora-specific patch), and (after another month) packages
went to updates-testing, where they've been for another two months.

- hal-info - BZ 425875
I found what amounts to a typo (my system listed in a comment but not
in the actual config) and got no response. After a month, I went
upstream (created an upstream BZ account, etc.), and it was fixed
there. It appears a newer hal-info will be in F9, but a month after
I reported the fix in RH BZ, there's no sign of an update for F8.
There has never been a response from anybody in RH BZ.

- hal - BZ 425876
hal is required for NetworkManager, but they both have startup
priority 98. Changing the system LC_COLLATE to anything that cares
about case breaks startup; hal should probably be below 98. I guess
upstart is supposed to fix all this, but when? Again, never a
response from a maintainer in BZ. At least if no change will be made,
say so and close the bug.

- system-config-network - BZ 429725
This one a s-c-n developer jumped in quickly and provided a patch in
short order (and the fix is in s-c-n git). I verified it fixed the
problem, but there's no sign of an actual update for F8 two months
later.

I don't want to get automated triage emails about any of these after
they've been idle for months or years. NEEDINFO does not apply (at
least as far as I can tell - nobody has asked for any more info anyway).
Any email alerts for these need to go to the maintainers, not the
reporters.

I understand people are busy (I never get done all I'd like to), but why
should I report bugs, research and supply fixes, when still nothing
happens?

--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-05-2008, 12:53 AM
Andrew Farris
 
Default Reverse bug triage

Chris Adams wrote:

I don't want to get automated triage emails about any of these after
they've been idle for months or years. NEEDINFO does not apply (at
least as far as I can tell - nobody has asked for any more info anyway).
Any email alerts for these need to go to the maintainers, not the
reporters.

I understand people are busy (I never get done all I'd like to), but why
should I report bugs, research and supply fixes, when still nothing
happens?


The automated script has no way of knowing the specifics of these bugs; go
comment 'this still matters' and change them out of NEEDINFO. The bug triaging
team is following the best path forward they had decided upon; there is no
possible way for a scripted bugzilla cleaning tool to decide if all the
information is there to solve that bug.


--
Andrew Farris <lordmorgul@gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
revoked key 0xC99B1DF3 no longer used
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-05-2008, 01:06 AM
Chris Adams
 
Default Reverse bug triage

Once upon a time, Andrew Farris <lordmorgul@gmail.com> said:
> The automated script has no way of knowing the specifics of these bugs; go
> comment 'this still matters' and change them out of NEEDINFO. The bug
> triaging team is following the best path forward they had decided upon;
> there is no possible way for a scripted bugzilla cleaning tool to decide if
> all the information is there to solve that bug.

Do the triage messages just go to the requester or to everybody
(requester, maintainer, CCs)? If they only go to the requester, then
one rule to try would be if the last comment was from the requester,
send a notice to the maintainer. In most cases, if the requester was
the last person to comment, there's nothing more they can do unless
asked for more info.
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-05-2008, 01:18 AM
Kevin Kofler
 
Default Reverse bug triage

Chris Adams <cmadams <at> hiwaay.net> writes:
> Do the triage messages just go to the requester or to everybody
> (requester, maintainer, CCs)? If they only go to the requester, then
> one rule to try would be if the last comment was from the requester,
> send a notice to the maintainer. In most cases, if the requester was
> the last person to comment, there's nothing more they can do unless
> asked for more info.

They go to everybody who gets mail for that bug: requester, maintainer, CCs. I
properly triaged all the bugs I got mailed about due to the cleanup scripts,
either closed them or updated the version or just cleared the NEEDINFO if they
were filed against an old Rawhide, but still apply to the current one.

Unfortunately, they don't go to new comaintainers who got watchbugzilla only
after the bug was filed, so if you want to be sure those see the bug and can
act on it, you have to add them to the CC list. (This is something which should
probably be improved: when a new comaintainer gets watchbugzilla on a package,
they should get CCed automatically to the open bugs against the component, it
is tedious to go through all of them and click "add myself to the CC list" when
there are dozens of bugs (e.g. for kde*).)

Kevin Kofler

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-05-2008, 01:18 AM
Andrew Farris
 
Default Reverse bug triage

Chris Adams wrote:

Once upon a time, Andrew Farris <lordmorgul@gmail.com> said:
The automated script has no way of knowing the specifics of these bugs; go
comment 'this still matters' and change them out of NEEDINFO. The bug
triaging team is following the best path forward they had decided upon;
there is no possible way for a scripted bugzilla cleaning tool to decide if
all the information is there to solve that bug.


Do the triage messages just go to the requester or to everybody
(requester, maintainer, CCs)? If they only go to the requester, then
one rule to try would be if the last comment was from the requester,
send a notice to the maintainer. In most cases, if the requester was
the last person to comment, there's nothing more they can do unless
asked for more info.


I think any comment posted to the bug should go out to all CC's, so I would
think anyone on the list got those messages including the maintainers. I'm not
positive whether there did or not, but unless CC's are specifically excluded it
should have.


Also, that idea is interesting but problematic for bugs where the original
reporter disappeared but a secondary commenter provided the necessary info. It
might have caught a few cases, but would have needed human review too because
some bugs that reporter comments back something like 'Ill look at this soon'
which really was not the requested info; that bug needs closed if they haven't
reported back the right info, so leaving it would be clutter that the triaging
missed.


--
Andrew Farris <lordmorgul@gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
revoked key 0xC99B1DF3 no longer used
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----

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

Thread Tools




All times are GMT. The time now is 03:49 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org