From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15214 invoked by alias); 2 Jan 2017 19:24:03 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22324 Received: (qmail 16594 invoked from network); 2 Jan 2017 19:24:03 -0000 X-Qmail-Scanner-Diagnostics: from know-smtprelay-omc-5.server.virginmedia.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(80.0.253.69):SA:0(-0.0/5.0):. Processed in 6.331716 secs); 02 Jan 2017 19:24:03 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.w.stephenson@ntlworld.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _smtprelay.virginmedia.com designates 80.0.253.69 as permitted sender) X-Originating-IP: [86.21.219.59] X-Spam: 0 X-Authority: v=2.1 cv=CMjXJkfD c=1 sm=1 tr=0 a=utowdAHh8RITBM/6U1BPxA==:117 a=utowdAHh8RITBM/6U1BPxA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=kj9zAlcOel0A:10 a=NTBXAtP2i9mayMa3nfoA:9 a=CjuIK1q_8ugA:10 Date: Mon, 2 Jan 2017 19:16:45 +0000 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: using gitlab (or other) issue tracker instead of mailing list? Message-ID: <20170102191645.6ef3ef23@ntlworld.com> In-Reply-To: <20170102153830.GA4752@fujitsu.shahaf.local2> References: <20170102153830.GA4752@fujitsu.shahaf.local2> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 2 Jan 2017 15:38:30 +0000 Daniel Shahaf 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