[dpdk-web] [PATCH] add the bug tracker in the development process
thomas at monjalon.net
Wed Nov 29 22:30:05 CET 2017
24/11/2017 22:09, Thomas Monjalon:
> Add two links to bugzilla in the dev page.
> The first link at the top redirects to the open bugs.
> The second link is provided in a new section about bug management.
> Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> dev.html | 8 ++++++++
> 1 file changed, 8 insertions(+)
> diff --git a/dev.html b/dev.html
> index 34f24cf..3253fdd 100644
> --- a/dev.html
> +++ b/dev.html
> @@ -45,6 +45,8 @@
> Coming patches are listed in <a href="/dev/patchwork">patchwork</a>.
> <p>Planned features are listed in the <a href="/dev/roadmap">roadmap</a>
> and integrated during a <a href="/dev/roadmap#cycle">cycle started by a merge window</a>.
> + <p>Bugs are open in <a
> + href="http://dpdk.org/tracker/buglist.cgi?bug_status=__open__&product=DPDK">bugzilla</a>.
> <h3 id="licenses">Licenses</h3>
> <p>Main code is BSD licensed and Linux kernel related parts are naturally licensed under the GPL.
> @@ -134,6 +136,12 @@
> <p>Most of the patchwork actions can be done
> with a <a href="/dev/patchwork/help/pwclient/">pwclient</a> command line.
> + <h3 id="bugzilla">Contribute by finding or fixing bugs</h3>
> + <p>There is a <a href="http://dpdk.org/tracker/">bug tracker</a> where
> + anybody can notify a bug to the community, and follow the resolution.
> + <p>A notification is sent to dev at dpdk.org for every new bug.
> + The fixes must be sent and discussed on the mailing list.
> <h3 id="board">Technical Board</h3>
> <p>The Technical Board may intermediate in the development process,
> as described in the <a href="/about/techboard">Technical Board operation</a>.
More information about the web