From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH] version: 19.05-rc0
Date: Wed, 06 Feb 2019 11:18:07 +0100 [thread overview]
Message-ID: <6918032.rztgTTVyso@xps> (raw)
In-Reply-To: <20190202153450.4705-1-thomas@monjalon.net>
Let's start a new release cycle!
I know it is uncommon to start so early in the month :)
The earlier we start, the less delay we will have.
This 19.05 release is expected to be big.
We must be very active in reviews.
Note: providing some reviews increases your chances to be reviewed.
Thank you
02/02/2019 16:34, Thomas Monjalon:
> doc/guides/rel_notes/index.rst | 1 +
> doc/guides/rel_notes/release_19_05.rst | 210 ++++++++++++++++++++
> lib/librte_eal/common/include/rte_version.h | 6 +-
> meson.build | 2 +-
> 4 files changed, 215 insertions(+), 4 deletions(-)
> create mode 100644 doc/guides/rel_notes/release_19_05.rst
Applied
next prev parent reply other threads:[~2019-02-06 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 15:34 Thomas Monjalon
2019-02-06 10:18 ` Thomas Monjalon [this message]
2019-02-06 10:18 ` Mcnamara, John
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=6918032.rztgTTVyso@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).