Suggested improvements to the release-critical bug tracker - Debian

This is a discussion on Suggested improvements to the release-critical bug tracker - Debian ; Hello, I've noticed that most issues tracked on the release-critical bug tracker [1] are actually already fixed in unstable. This is leading to the perception there are an enormous number of unfixed release-critical issues for lenny (298 currently). And it ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Suggested improvements to the release-critical bug tracker

  1. Suggested improvements to the release-critical bug tracker

    Hello,

    I've noticed that most issues tracked on the release-critical bug
    tracker [1] are actually already fixed in unstable. This is leading
    to the perception there are an enormous number of unfixed
    release-critical issues for lenny (298 currently). And it makes it
    harder to figure out which issues actually need attention (you have to
    look at each bug report separately to figure which do and do not have
    fixed versions in unstable). Currently, there are probably less than
    50 unfixed bugs, but it appears that there are six times that many.
    The other 250 are already fixed in unstable, and waiting to migrate to
    testing.

    I suggest that, by default, the release-critical tracker page list
    only those bugs that do not have a fix uploaded yet (make it optional
    to list all current RC issues). Also, I suggest that the page tracks
    the "Number concerning the next release with no fix currently
    uploaded" and "Number that have already been fixed in unstable that
    are currently waiting to migrate to testing" rather than just "Number
    concerning the next release". Also, I suggest that these two curves
    get added to the graph on the main RC bug tracker page.

    Another suggestion: some of the bug titles on the detailed RC bug
    tracker page [2] have a green or orange font, meaning patch (+) or
    help (H). It would be useful for that to be explained on the page, or
    have the explaination for + and H colored at the top.

    And another suggestion: I suggest that the the lists of opened and
    closed bugs be relative to midnight starting the current 24 hour day,
    rather than relative to the most recent update of the tracker page,
    which is every couple hours. The current way makes it seem that not
    much is going on every day, when really, a lot of progress is
    happening.

    Thank you for your consideration,
    Mike

    P.S. Please CC me on any replies as I am not subscribed to this list.

    [1] http://bugs.debian.org/release-critical
    [2] http://bugs.debian.org/release-critical/debian/all.html


    --
    To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: Suggested improvements to the release-critical bug tracker

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIzBi7mO5zOp3h7rERAtdSAJ4k6Sh1lK6+yB07tPtNAR 4+qOd2TwCghhQf
    i4TmPgZWuMkKxvIi5yg/CJE=
    =4Dp/
    -----END PGP SIGNATURE-----

  3. Re: Suggested improvements to the release-critical bug tracker

    On Sat, Sep 13, 2008 at 02:55:40PM -0400, Michael Gilbert wrote:
    > I've noticed that most issues tracked on the release-critical bug
    > tracker [1] are actually already fixed in unstable. This is leading
    > to the perception there are an enormous number of unfixed
    > release-critical issues for lenny (298 currently). And it makes it
    > harder to figure out which issues actually need attention (you have to
    > look at each bug report separately to figure which do and do not have
    > fixed versions in unstable). Currently, there are probably less than
    > 50 unfixed bugs, but it appears that there are six times that many.
    > The other 250 are already fixed in unstable, and waiting to migrate to
    > testing.


    Elaborating on Marc's response,
    http://bts.turmzimmer.net/details.ph...s&ignmerged=on
    shows 154 RC bugs that are outstanding in both testing and unstable.

    Which does not mean there are only 154 RC bugs that still need to be fixed -
    a number of the RC bugs that are fixed in unstable have been fixed in ways
    that are unsuitable for unblocking for the release, or have introduced new
    build failures that need to be resolved before the packages can propagate,
    and therefore still require attention.

    --
    Steve Langasek Give me a lever long enough and a Free OS
    Debian Developer to set it on, and I can move the world.
    Ubuntu Developer http://www.debian.org/
    slangasek@ubuntu.com vorlon@debian.org


    --
    To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Re: Suggested improvements to the release-critical bug tracker

    > Try the alternative interface on http://bts.turmzimmer.net, which
    > provides everything you proposed (and quite a bit more)


    Thanks, that is quite a bit more useful. Where can I send suggestions
    for improvements to turmzimmer? Will this service ever be adopted as
    the official debian RC bug tracker?


    --
    To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Re: Suggested improvements to the release-critical bug tracker

    On Tue, Sep 16, 2008 at 4:18 AM, Michael Gilbert
    wrote:
    > Thanks, that is quite a bit more useful. Where can I send suggestions
    > for improvements to turmzimmer? Will this service ever be adopted as
    > the official debian RC bug tracker?


    I think this is good idea.

    --
    Cheers,
    Kartik Mistry | 0xD1028C8D | IRC: kart_
    Homepage: people.debian.org/~kartik
    Blog.en: ftbfs.wordpress.com
    Blog.gu: kartikm.wordpress.com


    --
    To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Re: Suggested improvements to the release-critical bug tracker

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIz1mfmO5zOp3h7rERAizmAJwLvtJQ2EUIQGghzV+8+F AIWbdNJwCeL7v7
    p5La4XJZ4eKAFwpnhd/0ras=
    =CjYL
    -----END PGP SIGNATURE-----

+ Reply to Thread