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

Keep up with the world of bugzilla

Browse source
This commit is contained in:
Eitan Adler 2014-06-29 07:40:20 +00:00
parent f5e11c7f75
commit 84a6a0a338
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45148
1 changed files with 11 additions and 46 deletions

57
en_US.ISO8859-1/articles/committers-guide/article.xml
View file

@ -2906,21 +2906,16 @@ Relnotes: yes</programlisting>
</sect1>
<sect1 xml:id="gnats">
<title>GNATS</title>
<title>Bugzilla</title>
<para>The &os; Project utilizes <application>GNATS</application>
<para>The &os; Project utilizes <application>Bugzilla</application>
for tracking bugs and change requests. Be sure that if you
commit a fix or suggestion found in a
<application>GNATS</application> PR, you use
<command>edit-pr <replaceable>pr-number</replaceable></command>
on <systemitem>freefall</systemitem> to close it. It is also
commit a fix or suggestion found in the PR database to close it.
It is also
considered nice if you take time to close any PRs associated
with your commits, if appropriate. You can also make use of
&man.send-pr.1; yourself for proposing any change which you feel
should probably be made, pending a more extensive peer-review
first.</para>
with your commits, if appropriate.</para>
<para>You can find out more about <application>GNATS</application>
<para>You can find out more about <application>Bugzilla</application>
at:</para>
<itemizedlist>
@ -2930,35 +2925,11 @@ Relnotes: yes</programlisting>
Problem Report Handling Guidelines</link></para>
</listitem>
<listitem>
<para><uri
xlink:href="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html</uri></para>
</listitem>
<listitem>
<para><link
xlink:href="&url.base;/support.html">http://www.FreeBSD.org/support.html</link></para>
</listitem>
<listitem>
<para>&man.send-pr.1;</para>
</listitem>
</itemizedlist>
<para>You can run a local copy of GNATS, and then integrate the
&os; GNATS tree by creating an <application>rsync</application>
mirror. Then you can run GNATS commands locally, allowing you
to query the PR database without an Internet connection.</para>
<sect2>
<title>Mirroring the GNATS Tree</title>
<para>It is possible to mirror the GNATS database by installing
<package>net/rsync</package>, and
executing:</para>
<screen>&prompt.user; <userinput>rsync -va rsync://bit0.us-west.freebsd.org/FreeBSD-bit/gnats .</userinput></screen>
</sect2>
</sect1>
<sect1 xml:id="people">
@ -3958,12 +3929,9 @@ Relnotes: yes</programlisting>
Contributors List.</para>
<para>Close the PR if the port came in as a PR. To close
a PR, just do <command>edit-pr
<replaceable>PR#</replaceable></command> on
<systemitem>freefall</systemitem> and change the
<varname>state</varname> from <constant>open</constant>
to <constant>closed</constant>. You will be asked to
enter a log message and then you are done.</para>
a PR, change the state to <literal>Issue
Resolved</literal> and the resolution as
<literal>Fixed</literal>.</para>
</answer>
</qandaentry>
</qandadiv>
@ -4705,11 +4673,8 @@ bak/packages packages from last complete &lt;major_version&gt; run on &lt;arch&
Committers</title>
<para>A few people who have access to the &os; machines do not
have commit bits. For instance, the project is willing to give
access to the GNATS database to contributors who have shown
interest and dedication in working on Problem Reports.</para>
<para>Almost all of this document will apply to these developers
have commit bits. Almost all of this document will apply to
these developers
as well (except things specific to commits and the mailing list
memberships that go with them). In particular, we recommend
that you read:</para>