[dpdk-web] [RFC v2] Add LTS section on the roadmap page
bluca at debian.org
Tue Mar 6 20:45:00 CET 2018
On Tue, 2018-03-06 at 12:25 +0100, Thomas Monjalon wrote:
> 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 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.
> 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
Ok, done in v3, please have a look.
The release dates are tentative of course - I picked the mainline
release + 2 weeks.
More information about the web