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

[Luca Boccassi <bluca@debian.org>]

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