From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: using gitlab (or other) issue tracker instead of mailing list?
Date: Mon, 2 Jan 2017 19:16:45 +0000 [thread overview]
Message-ID: <20170102191645.6ef3ef23@ntlworld.com> (raw)
In-Reply-To: <20170102153830.GA4752@fujitsu.shahaf.local2>
On Mon, 2 Jan 2017 15:38:30 +0000
Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> For what it's worth, I do support having some list of bugs: we do from
> time to time run into bugs, but those that we don't patch immediately
> are only recorded in the list archives.
>
> Bug trackers are generally open to the public and so serve some user
> support role as well. However, as far as I know, the existing support
> channels work well, and only a "repository of known, acknowledged,
> unfixed bugs" functionality is missing.
>
> As Eric points out, we could simply start using Etc/BUGS to fill that
> functionality. Let's adopt the convention that every entry be tagged
> with an X-Seq number for ease of reference:
For what it's worth, I agree with all the above.
Just to repeat what Bart already says for form's sake: the crucial thing
missing for use of a more formal bug tracker is someone to operate it,
and anyone who reads the mailing list, can use a web interface and prod
the developers for info and has time to be diligent is suitable. None
of the usual suspects has time to be diligent enough to make it more tha
a millstone around the neck.
There's a similar danger with the BUGS file, of course, but it's easily
found and fixed and if we edit it ourselves it doesn't have the key
danger that someone raises a bug that then just sits doing nothing for
ever. (Of course, if no one fixes it is *does* sit around, but, to coin
a phrase, duh.)
pws
next prev parent reply other threads:[~2017-01-02 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM4j=kPgw=fLgEeCvV5xqpU9==o81riHj7RwowgQR3nwNnhZxA__37436.9124918759$1483233144$gmane$org@mail.gmail.com>
2017-01-02 15:38 ` Daniel Shahaf
2017-01-02 15:58 ` Frank Terbeck
2017-01-02 16:42 ` Daniel Shahaf
2017-01-02 16:27 ` Ray Andrews
2017-01-02 19:16 ` Peter Stephenson [this message]
2017-01-01 1:10 Timothee Cour
2017-01-02 21:42 ` Bart Schaefer
2017-01-12 17:34 ` Timothee Cour
2017-01-02 23:17 ` Axel Beckert
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=20170102191645.6ef3ef23@ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-users@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).