MANTIS
Mantis is the defect tracker system for the Austin Group. It is used
to collect written comments (defect reports) on specific documents.
Defect reports should be phrased wherever possible in terms of
specific wording changes. Comments submitted in this way can then be
more easily discussed at relevant working group meetings, or voted on
by email.
Mantis automatically processes comments submitted on the web at
http://www.austingroupbugs.net
Report Details should be entered as follows:
* First select an appropriate "Project"
* Then select the "Category", for 1003.1/Issue 7 this provides
a pulldown selection of the constituent volumes.
* You then should select the "Severity", selecting one from
Editorial
Comment
Objection
-------------------------------------------------
1. Objections
You should only classify an issue as an "objection" if you would vote
against approval of the submission if that issue is not resolved. Any
objection which is not supported by rationale, or which does not provide a
responsive proposal for resolution, will be deemed invalid, and reclassified
as a "comment".
2. Comments
If you wish to raise an issue where you believe that a better solution is
available, but the issue would not, on its own, cause you to vote against
approval of the submission if the issue were not resolved, you should
classify it as a "comment".
3. Editorials
Issues marked as editorial will not be discussed, they are included in this
mechanism as a simple way to bring such matters to the sponsors attention.
(If you see someone else classifying an issue as editorial, and you believe
it DOES need discussion or clarification, you should resubmit the point
yourself, with a different classification.)
-------------------------------------------------
* You should then select the Type of defect report , selecting from
Error
Omission
Clarification requested
Enhancement Request
There may be cases where the originator feels unable to provide
text, for example where a clarification is requested. In such
cases there are two possibilities:
- write down one of the possible alternatives. This at least
serves to illustrate your concern.
- contact someone else, in advance, who may be able to suggest
some wording.
Wording can be improved at the resolution meeting, but there
will not be time to create new wording, and no possibility
of subsequent off-line text generation. To emphasize:
CHANGE REQUESTS WITHOUT EXPLICIT EDITING INSTRUCTIONS WILL
BE REJECTED.
* Then enter Name, Organization and a User Reference
Note that it could be helpful for you to include a user identifier and
sequence number (eg DWC 25) in the User Reference field .
(note that you can define your own User Reference)
* Section
Section number or name, often the interface name
* Page Number
A range of pages can be specified as follows:
1-5
1,3,6-9
i-x
In the special case where you wish to raise a single issue
which has similar ramifications at many places in the
document, but which can be discussed together, it is helpful
if you state the first page instance and list later
instances in the defect report, for example:
In the Desired Action field:
-----------------------------------
Here and also at
page 344 line 52 section printf objection
page 344 line 53 section printf objection
page 346 line 92 section printf objection
page 381 line 40-41 section scanf objection
page 382 line 43 section scanf objection
Change "specifier" or "conversion specifier(s)" or
"conversion letter" to "conversion character(s)"
-------------------------------------------
* Line Number
Enter the line or range of lines, e.g
52
40-41
* Summary
Enter a one line summary of the defect report, e.g.
conversion specifiers in printf functions
* Description
Enter a precise description of the problem that explains why.
Be sure to add sufficient explanation for someone not
familiar with the problem to be able to make a decision.
For example:
---------------------------------------------------------
Terms used in printf, scanf, and similar interface specs are not
consistent. In various places the terms "conversion letter",
"conversion specifier", and "conversion character" are used
interchangeably. I believe the correct term is "conversion
character", as defined on page 344, line 59.
---------------------------------------------------------
* Desired Action
Be specific. For example:
Change "leftmost character"
to "first character in the string"
Another example:
----------------------------
Here and also at
page 344 line 52 section printf objection
page 344 line 53 section printf objection
page 346 line 92 section printf objection
page 381 line 40-41 section scanf objection
page 382 line 43 section scanf objection
Change "specifier" or "conversion specifier(s)" or
"conversion letter" to "conversion character(s)"
----------------------------------
(You can normally trust the editor to take care of formatting issues in such
changes, including use of the correct font et cetera, unless there is
something out of the ordinary)
Please DO NOT USE TABS, nor indent your text unnecessarily.
-------------------------- end of file -----------------------------------