[dpdk-web] [PATCH] add stable and LTS release plan

[dpdk-web] [PATCH] add stable and LTS release plan

[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.
---
 dev/roadmap.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index dfd5e41..3964422 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -91,6 +91,13 @@
 	integration deadline. Otherwise, they will be postponed to the next releases.
 	<p>At the end of the merge window, the first release candidate is out.
 	<p>The last period is 1 month long and is dedicated to bug fixing.
+	<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.
 	<h3 id="dates">Scheduling</h3>
 	<p>16.11
 	<ul>
-- 
1.9.0

Re: [dpdk-web] [PATCH] add stable and LTS release plan

[Thomas Monjalon]

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

> +	<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?

>  	<h3 id="dates">Scheduling</h3>

I think we should publish the dates for the next releases here.

Re: [dpdk-web] [PATCH] add stable and LTS release plan

[Mcnamara, John]

> -----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
> 
> > +	<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.).


> 
> >  	<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.

Re: [dpdk-web] [PATCH] add stable and LTS release plan

[Yuanhan Liu]

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

Re: [dpdk-web] [PATCH] add stable and LTS release plan

[Thomas Monjalon]

2017-02-28 15:02, Yuanhan Liu:
> On Fri, Feb 24, 2017 at 10:42:55AM +0000, Mcnamara, John wrote:
> > From: Thomas Monjalon
> > > >  	<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?

The next LTS should be announced in the roadmap.
The previous LTS can be marked in http://dpdk.org/rel.
Example:
DPDK 16.11 (LTS)   2016 November 13   06c1c577795360719d0b4fafaeee21e9