From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] version: 1.7.0-rc0
Date: Tue, 13 May 2014 16:23:55 +0200 [thread overview]
Message-ID: <4380699.AygicULADg@xps13> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA17C8D@IRSMSX103.ger.corp.intel.com>
> > Start development cycle for version 1.7.0.
> >
> > This new development workflow introduces a new versioning scheme.
> > Instead of having releases r0, r1, r2, etc, there will be release
> > candidates. Last number has special meanings:
> > < 16 numbers are reserved for release candidates (RTE_VER_SUFFIX is -rc)
> > 16 is reserved for the release (RTE_VER_SUFFIX must be unset)
> >
> > > 16 numbers can be used locally (RTE_VER_SUFFIX must be set)
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied for version 1.7.0
--
Thomas
prev parent reply other threads:[~2014-05-13 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 13:31 Thomas Monjalon
2014-05-12 19:41 ` Richardson, Bruce
2014-05-13 14:23 ` Thomas Monjalon [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=4380699.AygicULADg@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).