From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] version: 2.3.0-rc0
Date: Fri, 18 Dec 2015 19:50:15 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67480E49@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E544F065-EED4-47AD-A6BA-47E7885E3866@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wiles, Keith
> Sent: Friday, December 18, 2015 7:23 PM
> To: Thomas Monjalon; Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 1/2] version: 2.3.0-rc0
>
> On 12/18/15, 10:11 AM, "dev on behalf of Thomas Monjalon" <dev-
> bounces@dpdk.org on behalf of thomas.monjalon@6wind.com> wrote:
>
> >2015-12-18 12:11, Bruce Richardson:
> >> On Thu, Dec 17, 2015 at 12:16:30PM +0100, Thomas Monjalon wrote:
> >> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> >> > ---
> >> > lib/librte_eal/common/include/rte_version.h | 6 +++---
> >> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >> >
> >> > diff --git a/lib/librte_eal/common/include/rte_version.h
> b/lib/librte_eal/common/include/rte_version.h
> >> > index bb3e9fc..6b1890e 100644
> >> > --- a/lib/librte_eal/common/include/rte_version.h
> >> > +++ b/lib/librte_eal/common/include/rte_version.h
> >> > @@ -60,7 +60,7 @@ extern "C" {
> >> > /**
> >> > * Minor version number i.e. the y in x.y.z
> >> > */
> >> > -#define RTE_VER_MINOR 2
> >> > +#define RTE_VER_MINOR 3
> >> >
> >> > /**
> >> > * Patch level number i.e. the z in x.y.z
> >> > @@ -70,14 +70,14 @@ extern "C" {
> >> > /**
> >> > * Extra string to be appended to version number
> >> > */
> >> > -#define RTE_VER_SUFFIX ""
> >> > +#define RTE_VER_SUFFIX "-rc"
> >> >
> >> > /**
> >> > * Patch release number
> >> > * 0-15 = release candidates
> >> > * 16 = release
> >> > */
> >> > -#define RTE_VER_PATCH_RELEASE 16
> >> > +#define RTE_VER_PATCH_RELEASE 0
> >> >
> >> > /**
> >> > * Macro to compute a version number usable for comparisons
> >>
> >> What about the discussion about the numbering of DPDK versions in
> future? The
> >> latest suggest which was +1'ed a number of times was to use an
> Ubuntu-style
> >> YY.MM naming scheme. I don't think there was any objections to such a
> scheme
> >> so is it not premature to start naming the new release now using the
> old scheme?
> >
> >Before doing any change on master, it is better to change the version
> number
> >to avoid confusion with the previous release. Example, the generated
> doc does
> >not show 2.2 anymore.
> >
> >About changing the numbering, no problem, it can be changed at any time
> before
> >the RC1. At the moment there was a proposal for YY.MM and a proposal
> for 3.0.
> >Even the YY.MM needs more discussion as it is not clear if we should
> use 15.03
> >or 15.04 for the release ending at the end of March. It seems
> reasonnable to
> >expect a release the next day, i.e. in April.
>
> I believe the numbering should be 16.03, 16.06, 16.09 and 16.12. As for
> 2.2.0 we should give it a second name 15.12 == 2.2.0 (and add a label in
> Git), then we can start with 16.03 as the next release number. All
> efforts should be made to meet the months 3, 6, 9 and 12, if one happens
> to be into the next month for some reason then we still label and call
> it the correct release number.
When you say "the correct release number" I think you mean that if a release is planned for March but is actually completed in April, it would still be called 16.03. I believe Ubuntu take the opposite approach, and if a release does slip it gets the number for the month it's actually completed in (16.04 in this example). There are advantages and disadvantages to both approaches. We'll need to decide which approach is best.
The best way to avoid confusion it to move from planning releases for the end of a month to planning them for the start of a month. So, as Thomas suggested above, we shouldn't plan our next release for the end of March, but for the start of April instead. That way it becomes 16.04, and we have a month of leeway in case there is a slip.
>
> I would also suggest we label the 15.12 release as the Long Term Support
> (LTS), just to get a base line for the LTS. Then every 2 years(??) we
> have a new LTS release next one on 17.12, ...
+1 on this.
Tim
>
> Keith
> >
>
>
> Regards,
> Keith
>
>
>
next prev parent reply other threads:[~2015-12-18 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:16 Thomas Monjalon
2015-12-17 11:16 ` [dpdk-dev] [PATCH 2/2] doc: init next release notes Thomas Monjalon
2015-12-17 14:40 ` Mcnamara, John
[not found] ` <B27915DBBA3421428155699D51E4CFE2024090EB@IRSMSX103.ger.corp.intel.com>
2015-12-17 15:04 ` [dpdk-dev] [PATCH 1/2] version: 2.3.0-rc0 Thomas Monjalon
2015-12-18 12:11 ` Bruce Richardson
2015-12-18 16:11 ` Thomas Monjalon
2015-12-18 19:22 ` Wiles, Keith
2015-12-18 19:50 ` O'Driscoll, Tim [this message]
2015-12-18 20:12 ` Wiles, Keith
2015-12-18 20:43 ` 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=26FA93C7ED1EAA44AB77D62FBE1D27BA67480E49@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--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).