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 User

 
 
LinkBack Thread Tools
 
Old 02-13-2010, 11:47 PM
Bill Davidsen
 
Default Propigation of bug fixes

Bug https://bugzilla.redhat.com/show_bug.cgi?id=548989 was CLOSED on Jan 21st,
with the note that glibc-2.11.90-10 was in RAWHIDE. Should a bug be marked
CLOSED before the fix makes it into release?

My FC11 system, updated a few days ago, shows glibc-2.10.2-1.i686, and both my
FC12 machines have locked up and I haven't gone to reboot them. I am/will not
run RAWHIDE on those systems, FC12 is unstable enough.

The question is one of policy, should a bug be marked CLOSED before the average
user is FIXED? Meaning the fix is actually RELEASED.

Note: caps are not shouting, that's bugzilla speak as it was sent to me.

--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 02-13-2010, 11:55 PM
Tom Horsley
 
Default Propigation of bug fixes

On Sat, 13 Feb 2010 19:47:13 -0500
Bill Davidsen wrote:

> The question is one of policy, should a bug be marked CLOSED before the average
> user is FIXED? Meaning the fix is actually RELEASED.

Depends on who bugzilla is for :-).

If it is for developers, then they want to mark it closed
as soon as they actually get it fixed so they don't forget
to close it later, and so they don't get bugged by "open"
bugs that are already fixed.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 02-14-2010, 02:29 PM
Erik Hemdal
 
Default Propigation of bug fixes

> Date: Sat, 13 Feb 2010 19:47:13 -0500
> From: Bill Davidsen <davidsen@tmr.com>
> Subject: Propigation of bug fixes
>
> . . . .
>
> The question is one of policy, should a bug be marked CLOSED before the average
> user is FIXED? Meaning the fix is actually RELEASED.
>
>
I was curious about this one because CLOSED would naturally seem to
indicate that the user's problem is corrected; there is a VERIFIED state
that can indicate that QA has tested the fix successfully.

If you visit bugzilla.redhat.com and view a bug there, you can click on
the link for "Status". That will lead you eventually here (look for the
small link near the top of the page):

https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#CLOSED

where it looks like Fedora's definition of CLOSED lives. The status
values are used differently by RHEL and Fedora. There are several
possible resolutions that mean the current release will not -- or
perhaps cannot -- be fixed. It's also possible that a bug will be
closed by reporting it upstream.

By the way, the Life Cycle of a Bug shown here:

https://bugzilla.redhat.com/docs/en/html/lifecycle.html

looks like the default Bugzilla workflow, which doesn't seem to match
what Red Hat and Fedora actually use. But if I read this page, I would
agree with Bill.

Erik


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 02-15-2010, 07:53 PM
Bill Davidsen
 
Default Propigation of bug fixes

Tom Horsley wrote:
> On Sat, 13 Feb 2010 19:47:13 -0500
> Bill Davidsen wrote:
>
>> The question is one of policy, should a bug be marked CLOSED before the average
>> user is FIXED? Meaning the fix is actually RELEASED.
>
> Depends on who bugzilla is for :-).
>
> If it is for developers, then they want to mark it closed
> as soon as they actually get it fixed so they don't forget
> to close it later, and so they don't get bugged by "open"
> bugs that are already fixed.

Yes, if it was for users there would be a state indicating that a fix was being
tested. Of course now anyone else who still has the problem can report the bug,
which will be marked as a duplicate of the CLOSED bug.

If bugzilla was for actually fixing bugs there would be a script which reminds
someone that a fix has not been pushed, and it would be eventually. :-(

--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 

Thread Tools




All times are GMT. The time now is 04:34 PM.

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