From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] add the bug tracker in the development process
Date: Thu, 30 Nov 2017 02:40:14 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B82ED3B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2301009.brkiL0PioH@xps>
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>.
> >
>
>
next prev parent reply other threads:[~2017-11-30 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 21:09 Thomas Monjalon
2017-11-29 21:30 ` Thomas Monjalon
2017-11-30 2:40 ` Xu, Qian Q [this message]
2017-11-30 13:24 ` Thomas Monjalon
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=82F45D86ADE5454A95A89742C8D1410E3B82ED3B@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).