DPDK website maintenance
 help / color / mirror / Atom feed
* [dpdk-web] [PATCH] add the bug tracker in the development process
@ 2017-11-24 21:09 Thomas Monjalon
  2017-11-29 21:30 ` Thomas Monjalon
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Monjalon @ 2017-11-24 21:09 UTC (permalink / raw)
  To: web

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@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@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>.
-- 
2.15.0

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-web] [PATCH] add the bug tracker in the development process
  2017-11-24 21:09 [dpdk-web] [PATCH] add the bug tracker in the development process Thomas Monjalon
@ 2017-11-29 21:30 ` Thomas Monjalon
  2017-11-30  2:40   ` Xu, Qian Q
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Monjalon @ 2017-11-29 21:30 UTC (permalink / raw)
  To: web; +Cc: qian.q.xu

Any comment?

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@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@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>.
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-web] [PATCH] add the bug tracker in the development process
  2017-11-29 21:30 ` Thomas Monjalon
@ 2017-11-30  2:40   ` Xu, Qian Q
  2017-11-30 13:24     ` Thomas Monjalon
  0 siblings, 1 reply; 4+ messages in thread
From: Xu, Qian Q @ 2017-11-30  2:40 UTC (permalink / raw)
  To: Thomas Monjalon, web

Ok for me, thx. 

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, November 30, 2017 5:30 AM
> To: web@dpdk.org
> Cc: Xu, Qian Q <qian.q.xu@intel.com>
> Subject: Re: [dpdk-web] [PATCH] add the bug tracker in the development
> process
> 
> Any comment?
> 
> 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@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__&produ
> ct=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@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>.
> >
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-web] [PATCH] add the bug tracker in the development process
  2017-11-30  2:40   ` Xu, Qian Q
@ 2017-11-30 13:24     ` Thomas Monjalon
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Monjalon @ 2017-11-30 13:24 UTC (permalink / raw)
  To: Xu, Qian Q; +Cc: web

30/11/2017 03:40, Xu, Qian Q:
> Ok for me, thx. 

Applied

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-11-30 13:24 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-24 21:09 [dpdk-web] [PATCH] add the bug tracker in the development process Thomas Monjalon
2017-11-29 21:30 ` Thomas Monjalon
2017-11-30  2:40   ` Xu, Qian Q
2017-11-30 13:24     ` Thomas Monjalon

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).