From: x-fn-spp-ml@ntt-tx.co.jp
To: spp@dpdk.org, yasufum.o@gmail.com
Subject: [spp] [PATCH 1/1] docs: add bug report chapter
Date: Thu, 25 Jun 2020 17:01:15 +0900 [thread overview]
Message-ID: <20200625080115.19054-2-x-fn-spp-ml@ntt-tx.co.jp> (raw)
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
This patch adds how to issue bug using Bugzilla in RST document.
Also reference is addded from "CONTRIBUTING.txt".
Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Signed-off-by: Naoki Takada <ntakada14@gmail.com>
---
CONTRIBUTING.txt | 6 ++++++
docs/guides/bug_report.rst | 18 ++++++++++++++++++
docs/guides/index.rst | 1 +
3 files changed, 25 insertions(+)
create mode 100644 docs/guides/bug_report.rst
diff --git a/CONTRIBUTING.txt b/CONTRIBUTING.txt
index 957b7fb..3b24738 100644
--- a/CONTRIBUTING.txt
+++ b/CONTRIBUTING.txt
@@ -45,6 +45,12 @@ Coding Guidelines
* C code should follow the DPDK coding standards.
* Python code should follow PEP8.
+Bug report
+----------
+
+How to issue bug is described in "Bug report" chapter
+in the RST document.
+
Maintainer
----------
diff --git a/docs/guides/bug_report.rst b/docs/guides/bug_report.rst
new file mode 100644
index 0000000..e9064e3
--- /dev/null
+++ b/docs/guides/bug_report.rst
@@ -0,0 +1,18 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+ Copyright(c) 2020 Nippon Telegraph and Telephone Corporation
+
+Bug Report
+==========
+
+SPP is hosted project of DPDK.
+DPDK uses Bugzilla as its bug tracking system.
+
+Users can issue SPP related bugs in the following link:
+
+https://bugs.dpdk.org/enter_bug.cgi?product=SPP
+
+Note that to issue new bug, you have to create account to the Bugzilla.
+
+You can view open SPP related bugs in the following link:
+
+https://bugs.dpdk.org/buglist.cgi?bug_status=__open__&product=SPP
\ No newline at end of file
diff --git a/docs/guides/index.rst b/docs/guides/index.rst
index 70ec4a6..3ea80ef 100644
--- a/docs/guides/index.rst
+++ b/docs/guides/index.rst
@@ -15,6 +15,7 @@ SPP documentation
commands/index
tools/index
api_ref/index
+ bug_report
This documentation is the latest tagged version, but some of the latest
developing features might be not included.
--
2.17.1
next reply other threads:[~2020-06-25 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 8:01 x-fn-spp-ml [this message]
2020-06-30 6:51 ` Itsuro ODA
2020-07-01 14:46 ` Yasufumi Ogawa
2020-07-14 5:00 ` [spp] [PATCH v2 0/1] " x-fn-spp-ml
2020-07-14 15:33 ` Yasufumi Ogawa
2020-07-14 5:00 ` [spp] [PATCH v2 1/1] docs: " x-fn-spp-ml
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200625080115.19054-2-x-fn-spp-ml@ntt-tx.co.jp \
--to=x-fn-spp-ml@ntt-tx.co.jp \
--cc=spp@dpdk.org \
--cc=yasufum.o@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).