Re: [9front] PROPOSAL: New 9front Bug Tracker

[Eli Cohen <echoline@gmail.com>]

i don't think bug assignment matters that much. everyone does it, but
the point of these things is to document bugs and acknowledge repair

On Thu, Feb 8, 2018 at 7:31 PM,  <sl@stanleylieber.com> wrote:
> The draft proposal has been updated:
>
>         http://9front.org/bugtracker
>
> Diff follows:
>
> src/bugtracker:9,30 - /n/ewsd/usr/sl/www/werc/sites/9front.org/bugtracker:9,39
>                 the entirety of the discussion thread.
>
>         2.  A bug's status is defined by its location under one of the
> -       following directories:
> +       following top directories:
>
> -               a.  open/
> +               a.  new/
>
>                 b.  closed/
>
>                 c.  [tba]
>
> -       3.  A bug's priority is defined by [tba].
> +       3.  A bug's priority is defined by its location under one of
> +       the top directories listed in Definitions-2.
>
>         4.  A bug's assignment (the developer to which the bug is
>         assigned) is defined by [tba].
>
> +       5.  The subsystem to which a bug applies is defined by the
> +       contents of a file subsystem under the bug's top directory.
> +       Valid subsystems include:
> +
> +               a.  [tba]
> +
>   Features
>
> -       1.  Create and close bugs by sending an e-mail.
> +       1.  Create and close bugs by sending an e-mail.  In both cases
> +       the e-mail is forwarded to the regular 9front@9front.org
> +       mailing list.
>
>         2.  View bugs, their status, priority, and assignment via
>         command line tool, to be included with the default 9front



-- 
http://echoline.org