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

Move a block of text in preparation for it being rewritten. Translators

Browse source 
note: this is a copy with no text change (yet).
This commit is contained in:
Mark Linimon 2005-10-20 07:59:34 +00:00
parent 31360fdce5
commit b763b48719
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=26087
1 changed files with 19 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -138,6 +138,25 @@
or overheating processors — you should always try to rule or overheating processors — you should always try to rule
out these causes, whenever possible, before submitting a PR.</para> out these causes, whenever possible, before submitting a PR.</para>
<para>Next, you need to make sure your problem report goes to the
right people.</para>
<para>The first catch here is that if the problem is a bug in
third-party software (a port or a package you have installed), you
should report the bug to the original author, not to the &os;
Project. There are two exceptions to this rule: the first is if
the bug does not occur on other platforms, in which case the
problem may lie in how the software was ported to &os;; the
second is if the original author has already fixed the bug and
released a patch or a new version of his software, and the
&os; port has not been updated yet.</para>
<para>The second catch is that &os;'s bug tracking system sorts
problem reports according to the category the originator
selected. Therefore, if you select the wrong category when you
submit your problem report, there is a good chance that it will
go unnoticed for a while, until someone re-categorizes it.</para>
<para>Then you should ascertain whether or not the problem is <para>Then you should ascertain whether or not the problem is
timely. There are few things timely. There are few things
that will annoy a developer more than receiving a problem report that will annoy a developer more than receiving a problem report
@ -224,25 +243,6 @@
are also available via CVSweb.</para> are also available via CVSweb.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>Next, you need to make sure your problem report goes to the
right people.</para>
<para>The first catch here is that if the problem is a bug in
third-party software (a port or a package you have installed), you
should report the bug to the original author, not to the &os;
Project. There are two exceptions to this rule: the first is if
the bug does not occur on other platforms, in which case the
problem may lie in how the software was ported to &os;; the
second is if the original author has already fixed the bug and
released a patch or a new version of his software, and the
&os; port has not been updated yet.</para>
<para>The second catch is that &os;'s bug tracking system sorts
problem reports according to the category the originator
selected. Therefore, if you select the wrong category when you
submit your problem report, there is a good chance that it will
go unnoticed for a while, until someone re-categorizes it.</para>
</section> </section>
<section id="pr-writing"> <section id="pr-writing">