8:55 a.m.
Why does it
have to take so long just to fix such a simple bug for which a fix is
provided?
its called PRIORITIES!!!!!!!!!!!!!!! I doubt very much that at this
point in beta cycle developers are concentrating on the rebuild ability
of the spec files. And I'd imagine that very simple build errors in the
spec file during the beta phase are not all that uncommon. The fixes to
the spec files for rebuilding will most likely get fixed sometime before
the actual release...but we are SO far away from that actual
release...this is still the first set of beta isos.
Not that I expect new pam rpms to be released for a single
BuildRequires, but a simple "this will be fixed in the next release" would
be nice.
Its a simple fix....it will get fixed...it might feel good to have a
conversation with a developer about it before it gets fixed...but that
is also a waste of developer time to write a comment to every single bug
report for every single simple spec file fix, or documentation fix or
whatever. Being that nice...doesn't scale. Your bug report clearly
doesn't require feedback....so be a little humble and sit back and
wait. If your bug makes it into the final beta isos, then you might
want to rattle your monkey cage a little to try to get some
attention...but right now I'm sure there are other more important
pressing matters that developers have to deal with...like vacation
time...this is august.
-jef"wouldn't it be fun to see what the typical number of new bugs a
typical red hat developer gets every week? I wonder how much time it
would time to write a "just to say hi" comment for each new bug"spaleta
7:02 p.m.
New subject: pam src rpm replaced?
Hi Jef,
Its a simple fix....it will get fixed...it might feel good to have a
conversation with a developer about it before it gets fixed...but that
is also a waste of developer time to write a comment to every single bug
report for every single simple spec file fix, or documentation fix or
whatever.
Since the bug has to be handled anyway the developer will eventually need
to give a short reply anyway. This is bug and fix need a simple "noticed,
will be added in the next release" type of answer.
so be a little humble and sit back and wait. If your
bug makes it into the final beta isos, then you might want to rattle your
monkey cage a little to try to get some attention...
:) Just asking. Point is I have another bug outstanding with the same
maintainer for a year now and that one just needs to be closed
"CURRENTRELEASE" or "DUPLICATE" or something. I don't think I
should close
it although I guess I could. I feel the maintainer should pick the right
close status.
wouldn't it be fun to see what the typical number of new bugs a
typical red hat developer gets every week?
Yes, I would be interested to know this as well.
Bye,
Leonard.
--
How clean is a war when you shoot around nukelar waste?
Stop the use of depleted uranium ammo!
End all weapons of mass destruction.
2:10 a.m.
New subject: pam src rpm replaced?
On Sat, 23 Aug 2003, Jef Spaleta wrote:
-jef"wouldn't it be fun to see what the typical number of new
bugs a
typical red hat developer gets every week? I wonder how much time it
would time to write a "just to say hi" comment for each new bug"spaleta
I guarantee you it wouldn't be fun. ;o)
For others interested:
Way too many people add comments to a bug report asking for a
status update on their reported problem, or some similar request.
In general, if a developer hasn't added any comments to a report,
there is no new status to report, and they will get to it in
time, depending on their various priorities. The more time spent
on adding frivolous comments or "no, it is not fixed yet, or I
would have updated this report" comments, the less time their is
to fix all of the frivolous bug reports. ;o)
--
Mike A. Harris ftp://people.redhat.com/mharris
OS Systems Engineer - XFree86 maintainer - Red Hat
7:43 a.m.
New subject: pam src rpm replaced?
On Sun, 2003-08-24 at 09:10, Mike A. Harris wrote:
On Sat, 23 Aug 2003, Jef Spaleta wrote:
>-jef"wouldn't it be fun to see what the typical number of new bugs a
>typical red hat developer gets every week? I wonder how much time it
>would time to write a "just to say hi" comment for each new
bug"spaleta
I guarantee you it wouldn't be fun. ;o)
For others interested:
Way too many people add comments to a bug report asking for a
status update on their reported problem, or some similar request.
In general, if a developer hasn't added any comments to a report,
there is no new status to report, and they will get to it in
time, depending on their various priorities. The more time spent
Despite that (and that is my personal opinion), if a serious bug doesn't
get accepted (i.e. stays NEW) for several months (or isn't active for a
very long time) giving a heads up to the developer (maybe as a PM) might
be justifiable.
On the other hand, I don't consider a missing BuildRequires: as serious
;-).
Nils
--
Nils Philippsen / Red Hat / nphilipp(a)redhat.com
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
8:16 a.m.
New subject: pam src rpm replaced?
On Sun, 24 Aug 2003, Nils Philippsen wrote:
[...]
On the other hand, I don't consider a missing BuildRequires: as
serious
;-).
Sure, but as the fix seems to be trivial, I just can't figure out why
anybody wouldn't be just fixing these issues ASAP, just to get rid of them
if nothing else.
.. at least, any open issues trouble me, and the easiest fix is well...
fixing them.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
8:23 a.m.
New subject: pam src rpm replaced?
On Sun, 24 Aug 2003, Pekka Savola wrote:
On Sun, 24 Aug 2003, Nils Philippsen wrote:
[...]
> On the other hand, I don't consider a missing BuildRequires: as serious
> ;-).
Sure, but as the fix seems to be trivial, I just can't figure out why
anybody wouldn't be just fixing these issues ASAP, just to get rid of them
if nothing else.
There are many reasons why one might not jump and fix trivial
issues immediately. I know because there are numerous trivial
issues reported against XFree86 in bugzilla, some of them
reported by myself so I don't forget about them. Every fix has
some amount of overhead, and some amount of thought that needs to
be put into it.
At the same time, I don't think a developer needs to justify why
a given reported bug hasn't been fixed or closed in some manner
or another, as that wastes a tonne of time for no real good
reason.
.. at least, any open issues trouble me, and the easiest fix is
well... fixing them.
There are around 400 bugs on my plate right now personally. I've
got priorities, and when I'm done one high priority, the next
thing I'm looking for is the next high priority. You know, the
ones I will have a manager, and perhaps people higher in command
breathing fire down my neck if I don't get them fixed right away.
When someone has priorties, by definition things of a trivial
nature aren't necessarily high priority. And 10 "trivial" things
can easily eat up a day or two. They often "appear" trivial, but
end up being non-trivial. That happens quite often in fact.
But I digress...
Feel free to add the trivial keyword to the keywords field on any
bugs you consider that trivial. "EasyFix" is the keyword I
think, but look it up in help to be sure. Anyone who is in a
"fix trivial bugs" mood with time to spare and no fire breathing
manager behind their chair, could have a field day perhaps.
--
Mike A. Harris ftp://people.redhat.com/mharris
OS Systems Engineer - XFree86 maintainer - Red Hat
10:06 a.m.
New subject: pam src rpm replaced?
Hi Pekka,
Sure, but as the fix seems to be trivial, I just can't figure out
why
anybody wouldn't be just fixing these issues ASAP, just to get rid of them
if nothing else.
.. at least, any open issues trouble me, and the easiest fix is well...
fixing them.
Am I glad that somebody seems to be taking my side here :-).
Bye,
Leonard.
--
How clean is a war when you shoot around nukelar waste?
Stop the use of depleted uranium ammo!
End all weapons of mass destruction.
8:16 a.m.
New subject: pam src rpm replaced?
On Sun, 24 Aug 2003, Nils Philippsen wrote:
> Way too many people add comments to a bug report asking for a
> status update on their reported problem, or some similar request.
> In general, if a developer hasn't added any comments to a report,
> there is no new status to report, and they will get to it in
> time, depending on their various priorities. The more time spent
Despite that (and that is my personal opinion), if a serious bug doesn't
get accepted (i.e. stays NEW) for several months (or isn't active for a
very long time) giving a heads up to the developer (maybe as a PM) might
be justifiable.
You believe that all developers look at bugzilla emails? ;o) I
know most do, but I'm convinced that some have bad procmail
filters. ;o)
On the other hand, I don't consider a missing BuildRequires: as
serious
;-).
Generally speaking no, but there are some cases where it is bad.
;o)
--
Mike A. Harris ftp://people.redhat.com/mharris
OS Systems Engineer - XFree86 maintainer - Red Hat
7602
days inactive
7603
days old
7 comments
5 participants
participants (5)
-
Jef Spaleta -
Leonard den Ottolander -
Mike A. Harris -
Nils Philippsen -
Pekka Savola