[dpdk-web] [RFC] Add LTS section on the roadmap page

[dpdk-web] [RFC] Add LTS section on the roadmap page

[Luca Boccassi]

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 dev/roadmap.html | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index a2fea2f..c818bde 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -111,5 +111,15 @@
 		<li>Integration deadline: September 28, 2018
 		<li>Release: November 2, 2018
 	</ul>
+	<h3 id="lts">LTS releases</h3>
+	<p>LTS point releases follow mainline releases.
+	<p>After each -rc tag and after the final version, relevant bug fixes get
+        backported by the LTS maintainers into the respective branches.
+	<p>Developers can provide LTS-specific patches by sending them to stable@dpdk.org
+        only.
+	<p>After all the relevant bugfixes have been backported, regression tests are ran,
+        and if clear, the LTS is announced.
+	<p>Typically a new LTS version follows a mainline release by 1-2 weeks, depending
+        on the test results.
 </section>
 <footer></footer>
-- 
2.14.2

Re: [dpdk-web] [RFC] Add LTS section on the roadmap page

[Luca Boccassi]

On Thu, 2018-02-08 at 18:21 +0000, Luca Boccassi wrote:
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
>  dev/roadmap.html | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/dev/roadmap.html b/dev/roadmap.html
> index a2fea2f..c818bde 100644
> --- a/dev/roadmap.html
> +++ b/dev/roadmap.html
> @@ -111,5 +111,15 @@
>  		<li>Integration deadline: September 28, 2018
>  		<li>Release: November 2, 2018
>  	</ul>
> +	<h3 id="lts">LTS releases</h3>
> +	<p>LTS point releases follow mainline releases.
> +	<p>After each -rc tag and after the final version, relevant
> bug fixes get
> +        backported by the LTS maintainers into the respective
> branches.
> +	<p>Developers can provide LTS-specific patches by sending
> them to stable@dpdk.org
> +        only.
> +	<p>After all the relevant bugfixes have been backported,
> regression tests are ran,
> +        and if clear, the LTS is announced.
> +	<p>Typically a new LTS version follows a mainline release by
> 1-2 weeks, depending
> +        on the test results.
>  </section>
>  <footer></footer>

Thomas,

Is this what you had in mind? Let me know if there are any changes
you'd like.

And also please test how it looks before applying :-)

-- 
Kind regards,
Luca Boccassi

Re: [dpdk-web] [RFC] Add LTS section on the roadmap page

[Thomas Monjalon]

08/02/2018 19:24, Luca Boccassi:
> On Thu, 2018-02-08 at 18:21 +0000, Luca Boccassi wrote:
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > ---
> >  dev/roadmap.html | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/dev/roadmap.html b/dev/roadmap.html
> > index a2fea2f..c818bde 100644
> > --- a/dev/roadmap.html
> > +++ b/dev/roadmap.html
> > @@ -111,5 +111,15 @@
> >  		<li>Integration deadline: September 28, 2018
> >  		<li>Release: November 2, 2018
> >  	</ul>
> > +	<h3 id="lts">LTS releases</h3>
> > +	<p>LTS point releases follow mainline releases.
> > +	<p>After each -rc tag and after the final version, relevant
> > bug fixes get
> > +        backported by the LTS maintainers into the respective
> > branches.
> > +	<p>Developers can provide LTS-specific patches by sending
> > them to stable@dpdk.org
> > +        only.
> > +	<p>After all the relevant bugfixes have been backported,
> > regression tests are ran,
> > +        and if clear, the LTS is announced.
> > +	<p>Typically a new LTS version follows a mainline release by
> > 1-2 weeks, depending
> > +        on the test results.
> >  </section>
> >  <footer></footer>
> 
> Thomas,
> 
> Is this what you had in mind? Let me know if there are any changes
> you'd like.

You should talk about stable releases, LTS being some of them.

In current process, patches are applied in burst after -rc, right?
I think this burst mode is important to highlight.

Please, could you add a roadmap for each branch?
The roadmap could show EOL dates and the LTS ones.

> And also please test how it looks before applying :-)

You can test with "make".
On my machine I use "make PYTHON2=python2".

Re: [dpdk-web] [RFC] Add LTS section on the roadmap page

[Luca Boccassi]

On Thu, 2018-02-08 at 21:42 +0100, Thomas Monjalon wrote:
> 08/02/2018 19:24, Luca Boccassi:
> > On Thu, 2018-02-08 at 18:21 +0000, Luca Boccassi wrote:
> > > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > > ---
> > >  dev/roadmap.html | 10 ++++++++++
> > >  1 file changed, 10 insertions(+)
> > > 
> > > diff --git a/dev/roadmap.html b/dev/roadmap.html
> > > index a2fea2f..c818bde 100644
> > > --- a/dev/roadmap.html
> > > +++ b/dev/roadmap.html
> > > @@ -111,5 +111,15 @@
> > >  		<li>Integration deadline: September 28, 2018
> > >  		<li>Release: November 2, 2018
> > >  	</ul>
> > > +	<h3 id="lts">LTS releases</h3>
> > > +	<p>LTS point releases follow mainline releases.
> > > +	<p>After each -rc tag and after the final version,
> > > relevant
> > > bug fixes get
> > > +        backported by the LTS maintainers into the respective
> > > branches.
> > > +	<p>Developers can provide LTS-specific patches by
> > > sending
> > > them to stable@dpdk.org
> > > +        only.
> > > +	<p>After all the relevant bugfixes have been backported,
> > > regression tests are ran,
> > > +        and if clear, the LTS is announced.
> > > +	<p>Typically a new LTS version follows a mainline
> > > release by
> > > 1-2 weeks, depending
> > > +        on the test results.
> > >  </section>
> > >  <footer></footer>
> > 
> > Thomas,
> > 
> > Is this what you had in mind? Let me know if there are any changes
> > you'd like.
> 
> You should talk about stable releases, LTS being some of them.
> 
> In current process, patches are applied in burst after -rc, right?
> I think this burst mode is important to highlight.
> 
> Please, could you add a roadmap for each branch?
> The roadmap could show EOL dates and the LTS ones.

See v2 - I added the mention of the EOL dates, but release dates are
not fixed in stone given they immediately follow the mainline releases.
How would you like to see it worded?

> > And also please test how it looks before applying :-)
> 
> You can test with "make".
> On my machine I use "make PYTHON2=python2".

Ah great, thanks for the tip.

-- 
Kind regards,
Luca Boccassi

[dpdk-web] [RFC v2] Add LTS section on the roadmap page

[Luca Boccassi]

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 dev/roadmap.html | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index a2fea2f..dd13505 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -111,5 +111,20 @@
 		<li>Integration deadline: September 28, 2018
 		<li>Release: November 2, 2018
 	</ul>
+	<h2 id="stable">Stable releases</h2>
+	<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".
+	<p>Developers can provide stable-specific patches by sending them to stable@dpdk.org
+        only (avoiding dev@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.
+	<h3 id="stable">Stable releases roadmap</h3>
+	<p>16.11 is an LTS release, and is going to be maintained by Luca Boccassi until the end of
+        2018, with the latest point release following the release of 18.11 in November 2018.
+	<p>17.11 is an LTS release, and is going to be maintained by Yuanhan Liu until the end of
+        2019, with the latest point release following the release of 19.11 in November 2019.
 </section>
 <footer></footer>
-- 
2.14.2

Re: [dpdk-web] [RFC v2] Add LTS section on the roadmap page

[Thomas Monjalon]

Hi Luca,

Sorry I forgot this patch you sent one month ago.

09/02/2018 14:04, Luca Boccassi:
> +	<h2 id="stable">Stable releases</h2>
> +	<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".
> +	<p>Developers can provide stable-specific patches by sending them to stable@dpdk.org
> +        only (avoiding dev@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.

It is a good description of the current process.
When this patch is applied, I would like to discuss having a first
stable release before the next major release.

> +	<h3 id="stable">Stable releases roadmap</h3>

No need for this title if below is a table.

> +	<p>16.11 is an LTS release, and is going to be maintained by Luca Boccassi until the end of
> +        2018, with the latest point release following the release of 18.11 in November 2018.
> +	<p>17.11 is an LTS release, and is going to be maintained by Yuanhan Liu until the end of
> +        2019, with the latest point release following the release of 19.11 in November 2019.

We should include non LTS releases and make it a table:
	branch    next version    date    end of life    maintainer

Re: [dpdk-web] [RFC v2] Add LTS section on the roadmap page

[Luca Boccassi]

On Tue, 2018-03-06 at 12:25 +0100, Thomas Monjalon wrote:
> Hi Luca,
> 
> Sorry I forgot this patch you sent one month ago.

No worries.

> 09/02/2018 14:04, Luca Boccassi:
> > +	<h2 id="stable">Stable releases</h2>
> > +	<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".
> > +	<p>Developers can provide stable-specific patches by
> > sending them to stable@dpdk.org
> > +        only (avoiding dev@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.
> 
> It is a good description of the current process.
> When this patch is applied, I would like to discuss having a first
> stable release before the next major release.

Ok!

> > +	<h3 id="stable">Stable releases roadmap</h3>
> 
> No need for this title if below is a table.
> 
> > +	<p>16.11 is an LTS release, and is going to be maintained
> > by Luca Boccassi until the end of
> > +        2018, with the latest point release following the release
> > of 18.11 in November 2018.
> > +	<p>17.11 is an LTS release, and is going to be maintained
> > by Yuanhan Liu until the end of
> > +        2019, with the latest point release following the release
> > of 19.11 in November 2019.
> 
> We should include non LTS releases and make it a table:
> 	branch    next version    date    end of life    maintainer

Ok, done in v3, please have a look.

The release dates are tentative of course - I picked the mainline
release + 2 weeks.

-- 
Kind regards,
Luca Boccassi

[dpdk-web] [RFC v3] Add LTS section on the roadmap page

[Luca Boccassi]

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 dev/roadmap.html | 36 +++++++++++++++++++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 569d8b8..ebb81a9 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -37,7 +37,7 @@
 		</ul>
 	</nav>
 </header>
-<section>
+<section id="rel">
 	<h2>Development roadmap</h2>
 	<p>Major known features and milestones may be noted here.
 	This list is obviously neither complete nor guaranteed.
@@ -96,5 +96,39 @@
 		<li>Integration deadline: October 5, 2018
 		<li>Release: November 2, 2018
 	</ul>
+	<h2 id="stable">Stable releases</h2>
+	<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".
+	<p>Developers can provide stable-specific patches by sending them to stable@dpdk.org
+        only (avoiding dev@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.
+	<hr>
+	<table>
+		<tr>
+			<th>Branch</th>
+			<th>Next version</th>
+			<th>Date</th>
+			<th>End of life</th>
+			<th>Maintainer</th>
+		</tr>
+		<tr>
+			<td>16.11</td>
+			<td>16.11.6</td>
+			<td>May 19, 2018</td>
+			<td>November 2018</td>
+			<td>Luca Boccassi</td>
+		</tr>
+		<tr>
+			<td>17.11</td>
+			<td>17.11.2</td>
+			<td>May 19, 2018</td>
+			<td>November 2019</td>
+			<td>Yuanhan Liu</td>
+		</tr>
+	</table>
 </section>
 <footer></footer>
-- 
2.14.2

Re: [dpdk-web] [RFC v3] Add LTS section on the roadmap page

[Thomas Monjalon]

06/03/2018 20:43, Luca Boccassi:
> Signed-off-by: Luca Boccassi <bluca@debian.org>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Applied, thanks