DPDK website maintenance
 help / color / mirror / Atom feed
From: christian.ehrhardt@canonical.com
To: web@dpdk.org, Ian Stokes <ian.stokes@intel.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Luca Boccassi <bluca@debian.org>,
	Xueming Li <xuemingl@nvidia.com>,
	David Marchand <dmarchan@redhat.com>,
	Pei Zhang <pezhang@redhat.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	qian.q.xu@intel.com, Ju-Hyoung Lee <juhlee@microsoft.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	John McNamara <john.mcnamara@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	yuan.peng@intel.com, pingx.yu@intel.com, zhaoyan.chen@intel.com,
	Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [PATCH 0/2] Extend stable coverage on the roadmap
Date: Thu,  2 Dec 2021 11:18:20 +0100	[thread overview]
Message-ID: <20211202101822.3364418-1-christian.ehrhardt@canonical.com> (raw)

From: Christian Ehrhardt <christian.ehrhardt@canonical.com>

due to some constraints we will delay 19.11.11 a bit. But more
importantly we also intend to extend the lifetime of 19.11 LTS
by another year. That sounds great for users and downstream,
but it also needs resources for backports, test and validation.

Therefore this submission goes to a long recipient list of all
validation-contacts and release maintainers. I'd hope to get
a lot of sign-offs at least to patch 2 of this series representing
the ability and commitment to validate/test these additional
19.11.x releases, because without you we can not make them work.

For now this an experiment, but if it works out well quite likely
will be applied to later LTS (20.11, 21.11, ...) as well.

Christian Ehrhardt (2):
  Delay release of 19.11.11
  Extend 19.11.x support period to 3 years

 content/roadmap/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


             reply	other threads:[~2021-12-02 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 10:18 christian.ehrhardt [this message]
2021-12-02 10:18 ` [PATCH 1/2] Delay release of 19.11.11 christian.ehrhardt
2021-12-03 12:27   ` Luca Boccassi
2021-12-03 14:17   ` Kevin Traynor
2021-12-02 10:18 ` [PATCH 2/2] Extend 19.11.x support period to 3 years christian.ehrhardt
2021-12-03 12:28   ` Luca Boccassi
2021-12-03 14:17   ` Kevin Traynor
2021-12-08 16:16   ` Mcnamara, John
2021-12-14  7:55     ` Christian Ehrhardt
2021-12-14  8:02       ` Mcnamara, John
2021-12-14  8:38       ` Ali Alnubani
2021-12-16 10:56       ` Pei Zhang
2021-12-16 11:12         ` Christian Ehrhardt

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:

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

  git send-email \
    --in-reply-to=20211202101822.3364418-1-christian.ehrhardt@canonical.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dmarchan@redhat.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hariprasad.govindharajan@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=pingx.yu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=xuemingl@nvidia.com \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@intel.com \


* 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).