[dpdk-web] [PATCH] update stable releases roadmap

[Luca Boccassi]

On Thu, 2018-03-22 at 11:03 +0000, Luca Boccassi wrote:
> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote:
> > Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> > 
> > ---
> > This is at the same time, a call for volunteer,
> > and a proposed change to shorten the wait for the first stable
> > releases
> > from at least 3 months to 2 months.
> > 
> > Let's add this discussion to the agenda of the next techboard
> > meeting.
> > ---
> >  dev/roadmap.html | 35 +++++++++++++++++++++++++++++++----
> >  1 file changed, 31 insertions(+), 4 deletions(-)
> > 
> > diff --git a/dev/roadmap.html b/dev/roadmap.html
> > index e6cf640..e40f410 100644
> > --- a/dev/roadmap.html
> > +++ b/dev/roadmap.html
> > @@ -104,6 +104,8 @@
> >  		<li>Release: November 2, 2018
> >  	</ul>
> >  	<h2 id="stable">Stable releases</h2>
> > +	<p>There is a documentation page describing the
> > +	<a href="/doc/guides/contributing/stable.html">guidelines
> > of
> > the stable releases</a>.
> >  	<p>Stable point releases follow mainline releases.
> >  	<p>After each -rc tag and after the final version,
> > relevant
> > bug fixes get
> >  	backported by the stable maintainers into the respective
> > branches in "bursts".
> > @@ -111,8 +113,9 @@
> >  	to stable at dpdk.org only (avoiding dev at dpdk.org).
> >  	<p>After all the relevant bugfixes have been backported,
> >  	regression tests are ran, and if clear, the stable release
> > is announced.
> > -	<p>Typically a new stable release version follows a
> > mainline
> > release
> > -	by 1-2 weeks, depending on the test results.
> > +	<p>The first stable release (.1) of a branch should follow
> > +	its mainline release (.0) by two months,
> > +	before starting tests of the next mainline release
> > candidates.
> >  	<hr>
> >  	<div style="overflow-x:auto">
> >  	<table>
> > @@ -125,15 +128,39 @@
> >  		<tr>
> >  			<td>16.11.6</td>
> >  			<td>May 19, 2018</td>
> > -			<td>November 2018</td>
> > +			<td>November 2018 (LTS)</td>
> >  			<td>Luca Boccassi</td>
> >  		</tr>
> >  		<tr>
> >  			<td>17.11.2</td>
> >  			<td>May 19, 2018</td>
> > -			<td>November 2019</td>
> > +			<td>November 2019 (LTS)</td>
> >  			<td>Yuanhan Liu</td>
> >  		</tr>
> > +		<tr>
> > +			<td>18.02.1</td>
> > +			<td>April 6, 2018</td>
> > +			<td>June 2018</td>
> > +			<td>looking for volunteer</td>
> > +		</tr>
> > +		<tr>
> > +			<td>18.05.1</td>
> > +			<td>June 29, 2018</td>
> > +			<td>October 2018</td>
> > +			<td>looking for volunteer</td>
> > +		</tr>
> > +		<tr>
> > +			<td>18.08.1</td>
> > +			<td>October 5, 2018</td>
> > +			<td>January 2019</td>
> > +			<td>looking for volunteer</td>
> > +		</tr>
> > +		<tr>
> > +			<td>18.11.1</td>
> > +			<td>January 11, 2019</td>
> > +			<td>November 2020 (LTS)</td>
> > +			<td>looking for volunteer</td>
> > +		</tr>
> >  	</table>
> >  	</div>
> >  </section>
> 
> Hi,
> 
> I'm happy to help with 18.02.1.
> 
> Given it will be based on 18.05-rc2, which is due out on
> approximately
> April 20th, I think we can be ambitious and target April 27th as the
> tentative release date.
> 
> Note that ATT won't be able to help with regression tests this time
> around. John, may we count on help from Intel to run the usual batch
> of
> regression tests between the 20th and the 27th?

Slight misunderstanding, sorry - we'll want to base 18.02.1 on 18.05-
rc1 (not rc2), which means the dates get pulled forward by 10 days -
I'll make the branch available for review and eventually ask for help
from backporters if needed on April the 10th, and ambitiously targeting
release for April the 17th.
So we'd need regression tests done before the 17th of April.

-- 
Kind regards,
Luca Boccassi