From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Bug tracker for DPDK
Date: Thu, 27 Aug 2015 10:46:37 -0700 [thread overview]
Message-ID: <20150827104637.111e4871@urahara> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2022FD0EA@IRSMSX103.ger.corp.intel.com>
On Thu, 27 Aug 2015 10:28:45 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:
> Hi,
>
> Now that we are at the start of a release cycle it is a good time to talk about the need for a bug tracker for DPDK.
>
> As well as tracking defects it could be used to track upcoming or desired features/fixes.
>
> The most obvious tool for this is Bugzilla but other suggestions or ideas are welcome:
>
> https://www.bugzilla.org/
>
> John.
The problem with bug trackers is everyone has agree to use it.
Which is why Linux kernel developers treat bugzilla as read-only.
prev parent reply other threads:[~2015-08-27 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:28 Mcnamara, John
2015-08-27 17:46 ` Stephen Hemminger [this message]
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=20150827104637.111e4871@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).