Preferred way to report bugs that affect multiple RHL versions?

[Steve Bergman]

Hi,

I just reported a problem with the stock ticker applet.  Basically, it
looks like yahoo may have changed their format.  I reported it for RH9,
but it affects rawhide and probably all other versions with stock ticker
as well.

What is the preferred way to report a bug like this.  Bugzilla does not
allow selection of both RawHide and RedHat Linux, but duplicate bug
reports don't really make sense in this case.

Thanks,
Steve Bergman

[Hoyt]

On Friday 05 September 2003 03:41 pm, Steve Bergman wrote:
>  I just reported a problem with the stock ticker applet.  Basically,
> it
>  looks like yahoo may have changed their format. 
I would file it upstream as it's not an really app maintained by Red Hat, is 
it?

-- 
Hoyt

[Hans Deragon]

HoytDuff wrote:
>  On Friday 05 September 2003 03:41 pm, Steve Bergman wrote:
>  
> >I just reported a problem with the stock ticker applet.  Basically, it
> >looks like yahoo may have changed their format.
>  
>  
>  I would file it upstream as it's not an really app maintained by Red Hat, is 
>  it?
>   
Yahoo did change its format today.  I noticed it when I looked up my stocks.

You are somewhat right about flaging the problem upstream, but Red Hat should be 
made aware of the problem.  If the applet is broken, should it still be part of 
the next release?  Should it be removed?  RHL release should not be blocked by a 
faulty applet, but it tarnishes the image of RHL when installed applets 
installed.  Then again, the author might fix the applet 2 weeks after the new 
RHL was released.  The fixed rpm could then be made available.  It would be sad 
if an applet which might be usefull for many would be missing in a version only 
because of it was broked for a couple of weeks, because of bad timing.

What is the policy of Red Hat regarding this issue?


Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc.         Open source:
http://www.deragon.biz            http://swtmvcwrapper.sourceforge.net
mailto://[e-mail]         http://autopoweroff.sourceforge.net

[Alan Cox]

>  You are somewhat right about flaging the problem upstream, but Red
> Hat should be 
>  made aware of the problem.  If the applet is broken, should it still be part of 
>  the next release?  Should it be removed?  RHL release should not be blocked by a 
>  faulty applet, but it tarnishes the image of RHL when installed applets 
>  installed.  Then again, the author might fix the applet 2 weeks after the new 
>  RHL was released.  The fixed rpm could then be made available.  It would be sad 
>  if an applet which might be usefull for many would be missing in a version only 
>  because of it was broked for a couple of weeks, because of bad timing.
>  
>  What is the policy of Red Hat regarding this issue? 
File the bug against the most recent affected Red Hat is my suggestion and
do mention its in older ones. Also if its a gnome applet gnome-bugzilla
would be good because 2.4 is about to freeze..

[Owen Taylor]

On Fri, 2003-09-05 at 15:41, Steve Bergman wrote:
>  Hi,
>  
>  I just reported a problem with the stock ticker applet.  Basically, it
>  looks like yahoo may have changed their format.  I reported it for RH9,
>  but it affects rawhide and probably all other versions with stock ticker
>  as well.
>  
>  What is the preferred way to report a bug like this.  Bugzilla does not
>  allow selection of both RawHide and RedHat Linux, but duplicate bug
>  reports don't really make sense in this case. 
I'd just pick a version at random and mention in the body of the bug
report that it affects other versions.

I don't think most developers here pay that much attention to the
version for bug reports ... I certainly don't, anyways.

The important factors are:

 A) Does it still affect the development version?
 B) Is it important enough to consider doing an errata for?
 B') If so, does it affect old released versions?

Since the answer to B) is almost always "no", the B') seldom 
matters.

Regards,
					Owen

[ 
  I'm afraid our response to this bug is probably, at best, going to
  be to remove gtik from our packaging.
]