DPDK website maintenance
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, yliu@fridaylinux.org
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [RFC v2] Add LTS section on the roadmap page
Date: Tue, 06 Mar 2018 19:45:00 +0000	[thread overview]
Message-ID: <1520365500.27712.42.camel@debian.org> (raw)
In-Reply-To: <3266586.a8klAloIbi@xps>

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

  reply	other threads:[~2018-03-06 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 18:21 [dpdk-web] [RFC] " Luca Boccassi
2018-02-08 18:24 ` Luca Boccassi
2018-02-08 20:42   ` Thomas Monjalon
2018-02-09 13:05     ` Luca Boccassi
2018-02-09 13:04 ` [dpdk-web] [RFC v2] " Luca Boccassi
2018-03-06 11:25   ` Thomas Monjalon
2018-03-06 19:45     ` Luca Boccassi [this message]
2018-03-06 19:43   ` [dpdk-web] [RFC v3] " Luca Boccassi
2018-03-08 22:47     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1520365500.27712.42.camel@debian.org \
    --to=bluca@debian.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=yliu@fridaylinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).