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

Structure change to the PR-Guidelines article.

Browse source 
PR:		39055
Submitted by:	Chris Pepper <pepper@rockefeller.edu>
This commit is contained in:
Tom Rhodes 2002-07-17 19:10:53 +00:00
parent 6d67589994
commit 070aa0da56
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13655
1 changed files with 7 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
en_US.ISO8859-1/articles/pr-guidelines/article.sgml
View file

@ -60,14 +60,14 @@
<itemizedlist>
<listitem>
<para>The originator submits a PR and receives a confirmation
message.</para>
<para>The Reporter submits a PR and receives a confirmation
message, most likely via &man.send-pr.1; or the Problem Report web form at <ulink url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>.</para>
</listitem>
<listitem>
<para>Joe Random Committer takes interest in the PR and
assigns it to himself, or Jane Random BugBuster decides that
Joe is the best suited to handle it and assigns it to
Joe is best suited to handle it and assigns it to
him.</para>
</listitem>
@ -240,22 +240,21 @@
choose the one that contains the largest amount of useful
information and close the others, stating clearly the number
of the superseding PR. If several PRs contain non-overlapping
useful information, submit whatever is missing from the one
you keep open in a followup, with references to the PRs you
close.</para>
useful information, submit all the missing information to one
in a followup, including references to the others; then close the other PRs (which are now completely superseded).</para>
</section>
<section>
<title>Stale PRs</title>
<para>A PR is considered stale if it hasn't been modified in
more than six months. Apply the following procedure:</para>
more than six months. Apply the following procedure to deal with stale PRs:</para>
<itemizedlist>
<listitem>
<para>If the PR contains sufficient detail, try to reproduce
the problem in <literal>-CURRENT</literal> and
<literal>-STABLE</literal>. if you succeed, submit a
<literal>-STABLE</literal>. If you succeed, submit a
followup detailing your findings and try to find someone
to assign it to. Set the state to <quote>analyzed</quote>
if appropriate.</para>