DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-dev] Short term stable branches/releases
Date: Thu, 30 May 2019 11:10:41 +0100	[thread overview]
Message-ID: <f9343b8c-eb26-714e-44e7-8fc3835b95da@redhat.com> (raw)

Hi All,

A reminder that there is no longer a default in practice of having short
term stable branches/releases for xx.02/05/08 DPDK master releases.

Note, this is relevant for xx.02/05/08 based short term (~3 month)
stables only. DPDK LTS based off xx.11 is *not* changing.

This is to allow more time for maintenance and validation of master and
LTS branches/releases as it seems to be where the community are most
interested.

There can still be short term stable branches/releases for individual
xx.02/05/08 releases if there is a particular need and a commitment from
community members to maintain/validate.

See http://doc.dpdk.org/guides/contributing/stable.html#stable-releases
for further details.

thanks,
Kevin.

                 reply	other threads:[~2019-05-30 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f9343b8c-eb26-714e-44e7-8fc3835b95da@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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).