zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Debian bug triage
Date: Tue, 31 Jan 2012 01:10:58 +0100	[thread overview]
Message-ID: <87ty3c91f1.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAD77+gRQzHjqYx-k5X6y=Pd0QLD+pvp0Nj6jWUNoY_yFBBsAJw@mail.gmail.com> (Richard Hartmann's message of "Tue, 31 Jan 2012 00:38:22 +0100")

Richard Hartmann wrote:
[...]
> I am doing a bit or triage atm and was wondering if it would be OK to
> simply compile a list of still-valid bugs and dump the URLs on this
> list. The bug reports would already contain anything needed to
> reproduce. It would save work on my, and presumably your, side to keep
> the details in the reports and not copy & reformat them here.

FWIW, about a year ago, I compiled a list like that for debian's pkg-zsh
team:

  <http://lists.alioth.debian.org/pipermail/pkg-zsh-devel/2011-February/000018.html>

Since it's a year old, some of the bugs have been dealt with. But many
have not because frankly, spare time didn't permit it.

I sorted the outstanding bugs into a few categories with increasing
toughness and my two cents to each of them.

That list should be a decent start.

Most work is actually to identify which bugs are really legitimate bugs
still. Some may be fixed (I tried to sort them out at the time), some
maybe PEBCAK and others may be misunderstandings of zsh workings.

Anyway, I figured I'd mention that list, so you don't have to start with
nothing, if you're really planning to burn through all of those. At
least when I was done, I wasn't too keen on following up on my own
findings, because it took forever to get the list ready in the first
place. Maybe you can take this a little further. :-)

Regards, Frank


  reply	other threads:[~2012-01-31  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 23:38 Richard Hartmann
2012-01-31  0:10 ` Frank Terbeck [this message]
2012-01-31  9:47 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ty3c91f1.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).