os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move priority and severity into the "email template only section"

Browse source 
Approved by:	wblock
This commit is contained in:
Eitan Adler 2012-09-02 02:59:41 +00:00
parent e561dcd20f
commit bcfcea9dc0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=39486
1 changed files with 42 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

83
en_US.ISO8859-1/articles/problem-reports/article.sgml
View file

@ -646,7 +646,7 @@
adding one or more email addresses to the
<literal>Cc:</literal> header.</para>
<para>In the email template you will find the following two
<para>In the email template only, you will find the following
single-line fields:</para>
<itemizedlist>
@ -664,6 +664,47 @@
<application>CVSup</application>.</para>
</listitem>
<listitem>
<para><emphasis>Severity:</emphasis> One of
<literal>non-critical</literal>,
<literal>serious</literal> or
<literal>critical</literal>. Do not overreact; refrain
from labeling your problem <literal>critical</literal>
unless it really is (e.g. data corruption issues, serious
regression from previous functionality in -CURRENT)
or <literal>serious</literal> unless
it is something that will affect many users (kernel
panics or freezes; problems with
particular device drivers or system utilities). &os;
developers will not necessarily work on your problem faster
if you inflate its importance since there are so many other
people who have done exactly that &mdash; in fact, some
developers pay little attention to this field
because of this.</para>
<note>
<para>Major security problems should <emphasis>not</emphasis>
be filed in GNATS, because all GNATS information is public
knowledge. Please send such problems in private email to
&a.security-officer;.</para>
</note>
</listitem>
<listitem>
<para><emphasis>Priority:</emphasis> One of
<literal>low</literal>, <literal>medium</literal> or
<literal>high</literal>. <literal>high</literal> should
be reserved for problems that will affect practically
every user of &os; and <literal>medium</literal> for
something that will affect many users.</para>
<note>
<para>This field has become so widely abused that it is
almost completely meaningless.</para>
</note>
</listitem>
</itemizedlist>
<para>The next section describes fields that are common to both
@ -714,46 +755,6 @@
<literal>maintainer-update</literal>.</para>
</listitem>
<listitem>
<para><emphasis>Severity:</emphasis> One of
<literal>non-critical</literal>,
<literal>serious</literal> or
<literal>critical</literal>. Do not overreact; refrain
from labeling your problem <literal>critical</literal>
unless it really is (e.g. data corruption issues, serious
regression from previous functionality in -CURRENT)
or <literal>serious</literal> unless
it is something that will affect many users (kernel
panics or freezes; problems with
particular device drivers or system utilities). &os;
developers will not necessarily work on your problem faster
if you inflate its importance since there are so many other
people who have done exactly that &mdash; in fact, some
developers pay little attention to this field
because of this.</para>
<note>
<para>Major security problems should <emphasis>not</emphasis>
be filed in GNATS, because all GNATS information is public
knowledge. Please send such problems in private email to
&a.security-officer;.</para>
</note>
</listitem>
<listitem>
<para><emphasis>Priority:</emphasis> One of
<literal>low</literal>, <literal>medium</literal> or
<literal>high</literal>. <literal>high</literal> should
be reserved for problems that will affect practically
every user of &os; and <literal>medium</literal> for
something that will affect many users.</para>
<note>
<para>This field has become so widely abused that it is
almost completely meaningless.</para>
</note>
</listitem>
<listitem>
<para><emphasis>Category:</emphasis> Choose an appropriate
category.</para>