From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: add guideline for updating release notes
Date: Tue, 15 Sep 2015 09:33:41 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20233BF26@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2562266.rD95YcF0jU@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, September 15, 2015 10:13 AM
> To: Mcnamara, John
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: add guideline for updating release
> notes
>
> 2015-09-11 12:04, John McNamara:
> > From version 2.2 of DPDK onwards patchsets should include updates to
> > the Release Notes for additions, fixes and changes.
> >
> > Add guideline on what to update in the Release Notes to the
> > Documentation Contribution guidelines.
> >
> > Signed-off-by: John McNamara <john.mcnamara@intel.com>
>
> Applied, thanks.
>
> It is now expected to be an acceptance criteria during reviews.
>
> Any volunteer to fix the release notes for the previous commits?
> 17e01e3 i40e: fix base driver allocation when not using first numa node
> 45e73f4 ixgbe: remove burst size restriction of vector Rx
> b7fcd13 ixgbe: fix X550 DCB
> 7d49e0f hash: fix memory allocation of cuckoo key table
> 79db649 eal/linux: fix epoll timeout
Hi,
I'll fix the Release Notes based on the commit logs and CC the authors to ensure it is correct.
John
prev parent reply other threads:[~2015-09-15 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 11:04 John McNamara
2015-09-15 9:12 ` Thomas Monjalon
2015-09-15 9:33 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE20233BF26@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).