From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
Date: Thu, 8 Feb 2018 22:31:27 -0500 [thread overview]
Message-ID: <3D11D54F48BA3C150017F155D1B4259D@5ess.inri.net> (raw)
In-Reply-To: 797918FABB22A9492E3134BD9D4E04BA@5ess.inri.net
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
next reply other threads:[~2018-02-09 3:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 3:31 sl [this message]
2018-02-09 5:11 ` Eli Cohen
-- strict thread matches above, loose matches on Subject: below --
2018-02-09 3:21 sl
2018-02-09 3:15 sl
2018-02-09 3:01 sl
2018-02-08 2:55 sl
2018-02-08 1:34 sl
2018-02-08 2:08 ` [9front] " Lyndon Nerenberg
2018-02-08 8:37 ` Julius Schmidt
2018-02-08 9:07 ` Kurt H Maier
2018-02-08 16:54 ` Ethan Grammatikidis
2018-02-08 23:23 ` Steve Simon
2018-02-08 23:56 ` Kurt H Maier
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=3D11D54F48BA3C150017F155D1B4259D@5ess.inri.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.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.
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).