Changeset View
Changeset View
Standalone View
Standalone View
en_US.ISO8859-1/books/dev-model/book.xml
Context not available. | |||||
</copyright> | </copyright> | ||||
<revhistory> | <revhistory> | ||||
<revision> | <revision> | ||||
wblock: s/our/the/ seems better. | |||||
<revnumber>1.5</revnumber> | |||||
<date>October, 2014</date> | |||||
<revremark>Remove mention of GNATS which is no longer | |||||
used by the project.</revremark> | |||||
</revision> | |||||
<revision> | |||||
<revnumber>1.4</revnumber> | <revnumber>1.4</revnumber> | ||||
<date>September, 2013</date> | <date>September, 2013</date> | ||||
<revremark>Remove mention of CVS and CVSup which are no | <revremark>Remove mention of CVS and CVSup which are no | ||||
Context not available. | |||||
</para> | </para> | ||||
</section> | </section> | ||||
<section xml:id="role-gnats" xreflabel="GNATS Administrator"> | <section xml:id="role-bugmeister" xreflabel="Bugmeister"> | ||||
<title>GNATS Administrator</title> | <title>Bugmeister</title> | ||||
<para> | <para> | ||||
The GNATS Administrator is responsible for ensuring that the | The Bugmeister is responsible for ensuring that the | ||||
maintenance database is in working order, that the entries | maintenance database is in working order, that the entries | ||||
are correctly categorised and that there are no invalid entries. | are correctly categorised and that there are no invalid entries. | ||||
</para> | </para> | ||||
Context not available. | |||||
</para> | </para> | ||||
</section> | </section> | ||||
<section xml:id="role-bugmeister" xreflabel="Bugmeister"> | |||||
<title>Bugmeister</title> | |||||
<para> | |||||
The Bugmeister is the person in charge of the problem report | |||||
group. | |||||
</para> | |||||
<para> | |||||
Hat currently held by: | |||||
the Bugmeister Team <email>bugmeister@FreeBSD.org</email>, | |||||
</para> | |||||
</section> | |||||
<section xml:id="role-donations" xreflabel="Donations Liaison Officer"> | <section xml:id="role-donations" xreflabel="Donations Liaison Officer"> | ||||
<title>Donations Liaison Officer</title> | <title>Donations Liaison Officer</title> | ||||
<para> | <para> | ||||
Context not available. | |||||
someone's responsibility are collected on TODO-lists unless someone | someone's responsibility are collected on TODO-lists unless someone | ||||
volunteers to take the responsibility. All | volunteers to take the responsibility. All | ||||
requests, their distribution and follow-up are | requests, their distribution and follow-up are | ||||
handled by the <xref linkend="tool-gnats"/> tool. | handled by the <xref linkend="tool-bugzilla"/> tool. | ||||
</para> | </para> | ||||
<para> | <para> | ||||
Context not available. | |||||
<title>Problem reporting</title> | <title>Problem reporting</title> | ||||
<para> | <para> | ||||
FreeBSD comes with a problem reporting tool called | Before &os; 10, &os; included a problem reporting tool called | ||||
<quote>send-pr</quote> that is a part of the GNATS package. | <command>send-pr</command>. Problems include bug reports, | ||||
Not Done Inline ActionsIs send-pr still recommended? Does it even work on all supported releases? wblock: Is `send-pr` still recommended? Does it even work on all supported releases? | |||||
Not Done Inline Actionssend-pr is still supported on all releases that shipped before we switched to Bugzilla. i.e. it is supported in all supported releases right now, except for 9.3 which shipped after the changeover. We probably should not be recommending its use any more, however. gavin: send-pr is still supported on all releases that shipped before we switched to Bugzilla. i.e. | |||||
All users and developers are encouraged to use this tool for | feature requests, feature enhancements and notices of new versions | ||||
reporting problems in software they do not maintain. Problems | of external software that are included in the project. | ||||
include bug reports, feature requests, features that should be enhanced | Although <command>send-pr</command> is available, users and developers are encouraged | ||||
and notices of new versions of external software that is included | to submit issues using our <link xlink:href="https://bugs.freebsd.org/submit/"> | ||||
in the project. | problem report form</link>. | ||||
</para> | </para> | ||||
<para> | <para> | ||||
Problem reports are sent to an email address where it | Problem reports are sent to an email address where it | ||||
is inserted into the GNATS maintenance database. A | is inserted into the Problem Reports maintenance database. A | ||||
<xref linkend="role-bugbuster"/> | <xref linkend="role-bugbuster"/> | ||||
classifies the problem and sends it to the | classifies the problem and sends it to the | ||||
correct group or maintainer within the project. After someone | correct group or maintainer within the project. After someone | ||||
Context not available. | |||||
<para> | <para> | ||||
The major support tools for supporting the development process are | The major support tools for supporting the development process are | ||||
Perforce, GNATS, Mailman and OpenSSH. These are externally | Perforce, Bugzilla, Mailman, and OpenSSH. These are externally | ||||
Not Done Inline ActionsNeeds a serial comma. wblock: Needs a serial comma. | |||||
Not Done Inline ActionsSo you want it to read like this: If this is the case, I shall put it this way, however I strongly disagree. If this isn't the case, I'm not clear in what you are requesting to have done. jgh: So you want it to read like this:
Perforce, Bugzilla, Mailman, and OpenSSH
If this is the case… | |||||
developed tools and are commonly used in the open source world. | developed tools and are commonly used in the open source world. | ||||
</para> | </para> | ||||
Context not available. | |||||
</para> | </para> | ||||
</section> | </section> | ||||
<section xml:id="tool-gnats" xreflabel="GNATS"> | <section xml:id="tool-bugzilla" xreflabel="Bugzilla"> | ||||
<title>GNATS</title> | <title>Bugzilla</title> | ||||
<para> | <para> | ||||
GNATS is a maintenance database consisting of a set of tools to track bugs at a | Bugzilla is a maintenance database consisting of a set of tools to track bugs at a | ||||
central site. It supports the bug tracking process for sending | central site. It supports the bug tracking process for sending | ||||
and handling bugs as well as querying and updating the database | and handling bugs as well as querying and updating the database | ||||
and editing bug reports. The project uses one of its many client | and editing bug reports. The project uses one of its many client | ||||
interfaces, <quote>send-pr</quote>, to send | interfaces, <quote>send-pr</quote>, to send | ||||
<quote>Problem Reports</quote> by email to the | <quote>Problem Reports</quote> by email to the | ||||
projects central GNATS server. The committers have also web and | projects central Bugzilla server. The committers also have web and | ||||
Not Done Inline Actionss/have also/also have/ wblock: s/have also/also have/ | |||||
command-line clients available. | command-line clients. | ||||
Not Done Inline Actions"available" is not needed at all. wblock: "available" is not needed at all. | |||||
</para> | </para> | ||||
</section> | </section> | ||||
Context not available. |
s/our/the/ seems better.