lkml.org 
[lkml]   [2007]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: This is [Re:] How to improve the quality of the kernel[?].
    Oleg Verych wrote:
    > On Tue, Jun 19, 2007 at 04:27:15PM +0200, Stefan Richter wrote:
    >> There are different people involved in
    >> - patch handling,
    >> - bug handling (bugs are reported by end-users),
    >> therefore don't forget that PTS and BTS have different requirements.
    >
    > Sure. But if tracking was done, possible bugs where killed, user's bug
    > report seems to depend on that patch (bisecting), why not to have a
    > linkage here?

    Of course there are certain links between bugs and patches, and thus
    there are certain links between bug tracking and patch tracking.

    [...]
    > Current identification of problems and patch association
    > have completely zero level of tracking or automation, while Bugzilla is
    > believed by somebody to have positive efficiency in bug tracking.

    I, as maintainer of a small subsystem, can personally track bug--patch
    relationships with bugzilla just fine, on its near-zero level of
    automation and integration.

    Nevertheless, would a more integrated bug/patch tracking system help me
    improve quality of my output? ---
    a) Would it save me more time than it costs me to fit into the system
    (time that can be invested in actual debugging)?
    This can only be answered after trying it.
    b) Would it help me to spot mistakes in patches before I submit?
    No.
    c) Would I get quicker feedback from testers?
    That depends on whether such a system attracts testers and helps
    testers to work efficiently. This is also something that can only be
    speculated about without trying it.

    The potential testers that I deal with are mostly either very
    non-technical persons, or persons which are experienced in their
    hardware/application area but *not* in kernel internals and kernel
    development procedures.
    --
    Stefan Richter
    -=====-=-=== -==- =--==
    http://arcgraph.de/sr/
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-06-19 19:55    [W:4.105 / U:0.076 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site