Re: Development standards for unstable
On Thu, 12 Jan 2006, Thijs Kinkhorst wrote:
While the package might not be of the quality we strive to achieve within
Debian; if a bug is not release critical we consider the bug not to be
serious enough to impact the packages' releaseworthyness. This is by
definition. Even if there are many of those bugs, they appearently do not
prevent the core functionality from working.
Well the definition is given in policy and a policy change (to be discussed)
might change the definition of release critical. So if we define that
numbers N_n normal bugs and N_i important bugs and time spans T_n and
T_i where a bug is completely unattended by the maintainer (e.i. no
comments, no reason why not fixed, etc.) we can define a measure
X = Sum(N_n * T_n) + 2 * Sum(N_i * T_i)
and if this measure excedes a certain limit we define this as RC
critical. This is kind of formal and I have no idea whether this
is reasonable, but by this measure we (well, I know, somebody != me
would really have to do it) could write some automatic test that could
result in an RC bug filed against the package in question that can be
closed by closing (or commenting / give reasons) a number of the bugs
named above which brings the measure below the threshold we defined.
Just my 2 Euro cents
Andreas.
--
http://fam-tille.de
Reply to: