sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Added cross-reference to section for finding maintainers 

The "Tracking Bugs" section mentions how to enter a bug using
Bugzilla.  I added a new step just before the step that says
to submit the bug that tells the user to be sure to copy the
correct people.  The link goes to the section that describes
how to figure out who is responsible for code.

(From yocto-docs rev: 64e58402490267a339c9bade969850da50f39cf1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-04-15 09:02:28 -07:00 committed by Richard Purdie
parent a5d8b9ec17
commit 9ade10cfc4
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
documentation/dev-manual/dev-manual-newbie.xml
View File

@ -1088,9 +1088,11 @@
The "master" branch is the “upstream” repository where the final builds of the project occur.
The maintainer is responsible for allowing changes in from other developers and for
organizing the underlying branch structure to reflect release strategies and so forth.
<note>You can see who is the maintainer for Yocto Project files by examining the
<filename>maintainers.inc</filename> file in the Yocto Project
<filename>meta-yocto/conf/distro/include</filename> directory.</note>
<note>For information on finding out who is responsible (maintains)
for a particular area of code, see the
"<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
section.
</note>
</para>
<para>
@ -1251,6 +1253,11 @@
and so forth that surrounds the issue.
You can even attach supporting files for output from logs by
using the "Add an attachment" button.</para></listitem>
<listitem><para>Be sure to copy the appropriate people in the
"CC List" for the bug.
See the "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
section for information about finding out who is responsible
for code.</para></listitem>
<listitem><para>Submit the bug by clicking the "Submit Bug" button.</para></listitem>
</orderedlist>
</para>