public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Albert@HA-Schneider.de
To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org
Subject: gnats/364: Manual not up-to-date regarding states file
Date: Tue, 26 Mar 2002 03:00:00 -0000 [thread overview]
Message-ID: <E16pofL-00058D-00@fencepost.gnu.org> (raw)
>Number: 364
>Category: gnats
>Synopsis: Manual not up-to-date regarding states file
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 26 05:58:59 -0500 2002
>Originator: Hans-Albert Schneider
>Release: 3.999.1
>Organization:
GNATS FAQ maintainer
>Environment:
any
>Description:
The manual section "The states file" still describes
the 3.xxx states file. Notably, the new field "type"
is not mentioned.
Furthermore, the semantics have slightly changed: the last
state mentioned need not be *named* "closed" anymore (*1),
but needs to be of *type* closed (this is enforced, according
to the states file).
Similarly, the first state mentioned in the states file need
not be named "open" anymore (*1); it is the default state
for new PRs. It was not completely clear to me what is meant
by "default": Does this refer to the default installation,
i.e., can dbconfig define a different initail state?
Or is this refering to a scenario where a new PR already
bears a >State: field when it arrives?
Concerning the "type" field itself: the comments in file
states mention that two types ("open" and "closed") exist.
Please make clear whether something internally depends on
these two types, whether and how additional types can
be defined (just mention them in the file?), and what they
are useful for (transition logic like setting the
"Closed-Date"; more?).
(*1) To be precise, 3.1xx did not *require* the first and
last states given in gnats-adm/states to be called "open"
and "closed", but strongly suggested that for compatibility
reasons (some clients may expect...).
>How-To-Repeat:
>Fix:
Check with comments in the states and dbconfig files.
>Unformatted:
_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs
reply other threads:[~2002-03-26 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E16pofL-00058D-00@fencepost.gnu.org \
--to=hans-albert@ha-schneider.de \
--cc=bug-gnats@gnu.org \
--cc=gnats-prs@gnu.org \
--cc=pdm-gnats@zamazal.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 read-only IMAP folder(s) and NNTP newsgroup(s).