Re: using gitlab (or other) issue tracker instead of mailing list?

[Daniel Shahaf <d.s@daniel.shahaf.name>]

Timothee Cour wrote on Sat, Dec 31, 2016 at 17:10:43 -0800:
> Spawned off from a separate discussion:
> > regression: zsh completion stopped working after upgrading zsh 5.2=>5.3
> 
> What are your requirements for tracking zsh issues, and could this be
> accomplished by a standard issue tracker (eg github/gitlab/bitbucket)
> instead of this mailing list ?

Thanks for starting this thread.

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:

diff --git a/Etc/BUGS b/Etc/BUGS
index 9991ad9..96958f9 100644
--- a/Etc/BUGS
+++ b/Etc/BUGS
@@ -12,6 +12,13 @@ the nonomatch and nullglob options.
 ------------------------------------------------------------------------
 It is currently impossible to time builtins.
 ------------------------------------------------------------------------
-The comp* completion-related builtins (compadd, compset, etc) are run with
-$_comp_options in effect, rather than the user's options.
+40106: The comp* completion-related builtins (compadd, compset, etc) are
+run with $_comp_options in effect, rather than the user's options.
+------------------------------------------------------------------------
+40240: vcs_info: percent escapes in payloads are interpreted
+
+Example: hg branch names and quilt patch subjects that contain the literal
+string '%F{blue}', cause $vcs_info_msg_N_ to be rendered in blue.
+
+40240 has a patch, but 40241 explains why that patch is incomplete.
 ------------------------------------------------------------------------

... and to be clear, the venue for support questions and bug reporting
will [under this proposal] continue to be the zsh-users@ mailing list.

Cheers,

Daniel