mirror of
https://git.yoctoproject.org/poky
synced 2026-05-31 00:39:46 +00:00
dev-manual, ref-manual: Reorganized Bugzilla information
Fixes [YOCTO #11630] Reorganized the way the information about entering bugs using Bugzilla is arranged in the documentation set. The dev-manual now has a section that is purely procedural and steps the user through the process of logging a new bug in the Bugzilla system. The ref-manual has a conceptual section that introduces the YP implementation of Bugzilla by simply telling the user what it is and what what its purpose is. (From yocto-docs rev: 4bfba345010be7bc2866b819b9754bb06f93c91f) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
committed by
Richard Purdie
Richard Purdie
parent
0dae0865ba
commit
741dddf11a
@@ -1323,63 +1323,88 @@
|
|||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id='tracking-bugs'>
|
<section id='submitting-a-defect-against-the-yocto-project'>
|
||||||
<title>Tracking Bugs</title>
|
<title>Submitting a Defect Against the Yocto Project</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The Yocto Project uses its own implementation of
|
Use the Yocto Project implementation of
|
||||||
<ulink url='http://www.bugzilla.org/about/'>Bugzilla</ulink> to track bugs.
|
<ulink url='http://www.bugzilla.org/about/'>Bugzilla</ulink>
|
||||||
Implementations of Bugzilla work well for group development because they track bugs and code
|
to submit a defect (bug) against the Yocto Project.
|
||||||
changes, can be used to communicate changes and problems with developers, can be used to
|
For additional information on this implementation of Bugzilla see the
|
||||||
submit and review patches, and can be used to manage quality assurance.
|
"<ulink url='&YOCTO_DOCS_REF_URL;#resources-bugtracker'>Yocto Project Bugzilla</ulink>"
|
||||||
The home page for the Yocto Project implementation of Bugzilla is
|
section in the Yocto Project Reference Manual.
|
||||||
<ulink url='&YOCTO_BUGZILLA_URL;'>&YOCTO_BUGZILLA_URL;</ulink>.
|
For more detail on any of the following steps, see the Yocto Project
|
||||||
|
<ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>Bugzilla wiki page</ulink>.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Sometimes it is helpful to submit, investigate, or track a bug against the Yocto Project itself
|
Use the following general steps to submit a bug"
|
||||||
such as when discovering an issue with some component of the build system that acts contrary
|
|
||||||
to the documentation or your expectations.
|
|
||||||
Following is the general procedure for submitting a new bug using the Yocto Project
|
|
||||||
Bugzilla.
|
|
||||||
You can find more information on defect management, bug tracking, and feature request
|
|
||||||
processes all accomplished through the Yocto Project Bugzilla on the
|
|
||||||
<ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>wiki page</ulink>.
|
|
||||||
<orderedlist>
|
<orderedlist>
|
||||||
<listitem><para>Always use the Yocto Project implementation of Bugzilla to submit
|
<listitem><para>
|
||||||
a bug.</para></listitem>
|
Open the Yocto Project implementation of
|
||||||
<listitem><para>When submitting a new bug, be sure to choose the appropriate
|
<ulink url='&YOCTO_BUGZILLA_URL;'>Bugzilla</ulink>.
|
||||||
Classification, Product, and Component for which the issue was found.
|
</para></listitem>
|
||||||
Defects for the Yocto Project fall into one of seven classifications:
|
<listitem><para>
|
||||||
Yocto Project Components, Infrastructure, Build System & Metadata,
|
Click "File a Bug" to enter a new bug.
|
||||||
Documentation, QA/Testing, Runtime and Hardware.
|
</para></listitem>
|
||||||
Each of these Classifications break down into multiple Products and, in some
|
<listitem><para>
|
||||||
cases, multiple Components.</para></listitem>
|
Choose the appropriate "Classification", "Product", and
|
||||||
<listitem><para>Use the bug form to choose the correct Hardware and Architecture
|
"Component" for which the bug was found.
|
||||||
for which the bug applies.</para></listitem>
|
Bugs for the Yocto Project fall into one of several
|
||||||
<listitem><para>Indicate the Yocto Project version you were using when the issue
|
classifications, which in turn break down into several
|
||||||
occurred.</para></listitem>
|
products and components.
|
||||||
<listitem><para>Be sure to indicate the Severity of the bug.
|
For example, for a bug against the
|
||||||
Severity communicates how the bug impacted your work.</para></listitem>
|
<filename>meta-intel</filename> layer, you would choose
|
||||||
<listitem><para>Select the appropriate "Documentation change" item
|
"Build System, Metadata & Runtime", "BSPs", and
|
||||||
for the bug.
|
"bsps-meta-intel", respectively.
|
||||||
Fixing a bug may or may not affect the Yocto Project
|
</para></listitem>
|
||||||
documentation.</para></listitem>
|
<listitem><para>
|
||||||
<listitem><para>Provide a brief summary of the issue.
|
Choose the "Version" of the Yocto Project for which you found
|
||||||
Try to limit your summary to just a line or two and be sure to capture the
|
the bug (e.g. &DISTRO;).
|
||||||
essence of the issue.</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>Provide a detailed description of the issue.
|
<listitem><para>
|
||||||
You should provide as much detail as you can about the context, behavior, output,
|
Determine and select the "Severity" of the bug.
|
||||||
and so forth that surrounds the issue.
|
The severity indicates how the bug impacted your work.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
Choose the "Hardware" that the bug impacts.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
Choose the "Architecture" that the bug impacts.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
Choose a "Documentation change" item for the bug.
|
||||||
|
Fixing a bug might or might not affect the Yocto Project
|
||||||
|
documentation.
|
||||||
|
If you are unsure of the impact to the documentation, select
|
||||||
|
"Don't Know".
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
Provide a brief "Summary" of the bug.
|
||||||
|
Try to limit your summary to just a line or two and be sure
|
||||||
|
to capture the essence of the bug.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
Provide a detailed "Description" of the bug.
|
||||||
|
You should provide as much detail as you can about the context,
|
||||||
|
behavior, output, and so forth that surrounds the bug.
|
||||||
You can even attach supporting files for output from logs by
|
You can even attach supporting files for output from logs by
|
||||||
using the "Add an attachment" button.</para></listitem>
|
using the "Add an attachment" button.
|
||||||
<listitem><para>Be sure to copy the appropriate people in the
|
</para></listitem>
|
||||||
"CC List" for the bug.
|
<listitem><para>
|
||||||
See the "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
|
Click the "Submit Bug" button submit the bug.
|
||||||
section for information about finding out who is responsible
|
A new Bugzilla number is assigned to the bug and the defect
|
||||||
for code.</para></listitem>
|
is logged in the bug tracking system.
|
||||||
<listitem><para>Submit the bug by clicking the "Submit Bug" button.</para></listitem>
|
</para></listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
|
Once you file a bug, the bug is processed by the Yocto Project Bug
|
||||||
|
Triage Team and further details concerning the bug are assigned
|
||||||
|
(e.g. priority and owner).
|
||||||
|
You are the "Submitter" of the bug and any further categorization,
|
||||||
|
progress, or comments on the bug result in Bugzilla sending you an
|
||||||
|
automated email concerning the particular change or progress to the
|
||||||
|
bug.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
@@ -1551,7 +1576,8 @@
|
|||||||
</literallayout>
|
</literallayout>
|
||||||
Just provide the name of the file for which you are interested.
|
Just provide the name of the file for which you are interested.
|
||||||
The information returned is not ordered by history but does
|
The information returned is not ordered by history but does
|
||||||
include a list of all committers grouped by name.
|
include a list of everyone who has committed grouped by
|
||||||
|
name.
|
||||||
From the list, you can see who is responsible for the bulk of
|
From the list, you can see who is responsible for the bulk of
|
||||||
the changes against the file.
|
the changes against the file.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
|
|||||||
@@ -17,11 +17,41 @@
|
|||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id='resources-bugtracker'>
|
<section id='resources-bugtracker'>
|
||||||
<title>Tracking Bugs</title>
|
<title>Yocto Project Bugzilla</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
If you find problems with the Yocto Project, you should report them using the
|
The Yocto Project uses its own implementation of
|
||||||
Bugzilla application at <ulink url='&YOCTO_BUGZILLA_URL;'></ulink>.
|
<ulink url='http://www.bugzilla.org/about/'>Bugzilla</ulink> to track
|
||||||
|
defects (bugs).
|
||||||
|
Implementations of Bugzilla work well for group development because
|
||||||
|
they track bugs and code changes, can be used to communicate changes
|
||||||
|
and problems with developers, can be used to submit and review patches,
|
||||||
|
and can be used to manage quality assurance.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Sometimes it is helpful to submit, investigate, or track a bug against
|
||||||
|
the Yocto Project itself (e.g. when discovering an issue with some
|
||||||
|
component of the build system that acts contrary to the documentation
|
||||||
|
or your expectations).
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
A general procedure and guidelines exist for when you use Bugzilla to
|
||||||
|
submit a bug.
|
||||||
|
For information on how to use Bugzilla to submit a bug against the
|
||||||
|
Yocto Project, see the following:
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem><para>
|
||||||
|
The
|
||||||
|
"<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-defect-against-the-yocto-project'>Submitting a Defect Against the Yocto Project</ulink>"
|
||||||
|
section in the Yocto Project Development Manual.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>
|
||||||
|
The Yocto Project
|
||||||
|
<ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>Bugzilla wiki page</ulink>
|
||||||
|
</para></listitem>
|
||||||
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|||||||
@@ -1031,9 +1031,11 @@
|
|||||||
the Yocto Project implementation of
|
the Yocto Project implementation of
|
||||||
<ulink url='https://bugzilla.yoctoproject.org/'>Bugzilla</ulink>.
|
<ulink url='https://bugzilla.yoctoproject.org/'>Bugzilla</ulink>.
|
||||||
For general information on how to submit a bug against
|
For general information on how to submit a bug against
|
||||||
the Yocto Project, see the
|
the Yocto Project, see the Yocto Project Bugzilla
|
||||||
"<ulink url='&YOCTO_DOCS_DEV_URL;#tracking-bugs'>Tracking Bugs</ulink>"
|
<ulink url='&YOCTO_WIKI_URL;/wiki/Bugzilla_Configuration_and_Bug_Tracking'>wiki page</ulink>"
|
||||||
section in the Yocto Project Development Manual.
|
or the
|
||||||
|
<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-defect-against-the-yocto-project'>Submitting a Defect Against the Yocto Project</ulink>"
|
||||||
|
section, which is in the Yocto Project Development Manual.
|
||||||
<note>
|
<note>
|
||||||
The manuals might not be the right place to document
|
The manuals might not be the right place to document
|
||||||
variables that are purely internal and have a limited
|
variables that are purely internal and have a limited
|
||||||
|
|||||||
Reference in New Issue
Block a user