From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"web@dpdk.org" <web@dpdk.org>, "Liu, Yu Y" <yu.y.liu@intel.com>
Subject: Re: [dpdk-web] [PATCH] add stable and LTS release plan
Date: Tue, 28 Feb 2017 15:02:29 +0800 [thread overview]
Message-ID: <20170228070229.GN18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2026D5FB8@IRSMSX103.ger.corp.intel.com>
On Fri, Feb 24, 2017 at 10:42:55AM +0000, Mcnamara, John wrote:
>
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Friday, February 24, 2017 10:00 AM
> > To: Yuanhan Liu <yuanhan.liu@linux.intel.com>; Mcnamara, John
> > <john.mcnamara@intel.com>
> > Cc: web@dpdk.org; Liu, Yu Y <yu.y.liu@intel.com>
> > Subject: Re: [PATCH] add stable and LTS release plan
> >
> > Hi,
> >
> > Sorry there was no feedback on this patch.
> >
> > 2017-01-23 20:10, Yuanhan Liu:
> > > Cc: John McNamara <john.mcnamara@intel.com>
> > > Cc: Yu Liu <yu.y.liu@intel.com>
> > > Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> > > ---
> > >
> > > I made it in rush, meaning there are huge room for improvements
> > > about this short update :)
> > >
> > > Another thought from me is to link the detailed stable/LTS doc
> > > from John, when it's merged.
> >
> > It is merged: http://dpdk.org/doc/guides/contributing/stable.html
Good. I could make a v2 to point it.
> > > + <h3 id="stable">Stable and LTS release</h3>
> > > + <p>A new release will be made about every 3 months, shortly (about 3
> > > + weeks) after an upstream release is made. For example, v16.11.1 will
> > > + be released shortly after v17.02 is released.
> > > + <p>For a stable release, normally, there is only one such release.
> > > + While for a LTS release, which has longer maintainance (2 years),
> > > + there are more releases (.2, .3, etc) following.
> >
> > John, any opinion or rewording for this text?
>
> The wording id fine. The only thing is that "will be released" is in the
> future tense and 16.11.1 is due to be release. So it may be better as
> below. Also s/maintainance/maintenance/
>
>
> <h3 id="stable">Stable and LTS release</h3>
> <p>A new stable release will be made about every 3 months, shortly (around
> 3 weeks) after an upstream release has been made. For example, v16.11.1
> was released shortly after v17.02.
> <p>In general, there will only be one such release for a stable release.
> For an LTS release, which has a longer maintenance period (2 years)
> there will be several releases (.2, .3, etc.).
Thanks, John!
> >
> > > <h3 id="dates">Scheduling</h3>
> >
> > I think we should publish the dates for the next releases here.
>
> Agreed. Just add 3 weeks to the other release dates as a guidance.
Okay.
And I think we still miss one thing: we may need one new section to
tell which version is a LTS. Any idea?
--yliu
next prev parent reply other threads:[~2017-02-28 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 12:10 Yuanhan Liu
2017-02-24 9:59 ` Thomas Monjalon
2017-02-24 10:42 ` Mcnamara, John
2017-02-28 7:02 ` Yuanhan Liu [this message]
2017-02-28 9:10 ` 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=20170228070229.GN18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@dpdk.org \
--cc=yu.y.liu@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).