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

Mcnamara, John john.mcnamara at intel.com
Fri Feb 24 11:42:55 CET 2017



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, February 24, 2017 10:00 AM
> To: Yuanhan Liu <yuanhan.liu at linux.intel.com>; Mcnamara, John
> <john.mcnamara at intel.com>
> Cc: web at dpdk.org; Liu, Yu Y <yu.y.liu at 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 at intel.com>
> > Cc: Yu Liu <yu.y.liu at intel.com>
> > Signed-off-by: Yuanhan Liu <yuanhan.liu at 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.




More information about the web mailing list