Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473209
Andy Lindeberg <alindebe(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
--- Comment #13 from Andy Lindeberg <alindebe(a)redhat.com> 2008-12-15 13:03:13 EDT
---
And yet it is interesting to note that there are *zero* Fedora anaconda bug
reports in ON_DEV. Either this means that nobody is working on anything, or the
"official FESCO approved workflow" doesn't actually reflect the reality of
how
bugs get sorted. It should be fairly obvious which of these is the case.
So now the question is whether to abide by the official documentation, or to go
with the system that the rest of the people I work with actually use. I'd be
inclined to choose the latter in any case unless there was a really compelling
argument against it, and that's ignoring the fact that in /this case/
specifically, it's more helpful to this bug report for it to be marked as NEW
rather than ASSIGNED - /because/ the general interpretation is that ASSIGNED
means "Somebody is working on this bug", those bugs get less attention from
everybody but their assignees. For bugs that are /actually/ being worked on
that's not a problem, but for bugs that are still listed as assigned to
anaconda-maint-list, it can drastically reduce turnaround time. In contrast,
bugs marked as NEW are more likely to be looked at by non-assignees, increasing
the likelihood of a response, quick fix, or assignation for fixing.
In addition, having checked with clumens, that workflow is based around
releasing updates, which we don't do. It is, therefore, flawed.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.