From: Kevin Traynor <ktraynor@redhat.com>
To: dev@dpdk.org
Cc: bluca@debian.org, thomas@monjalon.net, david.marchand@redhat.com,
christian.ehrhardt@canonical.com, xuemingl@nvidia.com,
ferruh.yigit@amd.com, john.mcnamara@intel.com,
techboard@dpdk.org, Kevin Traynor <ktraynor@redhat.com>
Subject: [PATCH v2] doc: update LTS maintenance to 3 years
Date: Wed, 17 Jan 2024 16:24:19 +0000 [thread overview]
Message-ID: <20240117162419.223820-1-ktraynor@redhat.com> (raw)
In-Reply-To: <20240117161804.223582-1-ktraynor@redhat.com>
The existing official policy was to maintain LTS releases for 2 years.
19.11 and 20.11 LTS releases were maintained for 3 years and there was
not significant issues caused by code divergence from main etc.
Update the policy to indicate 3 years maintenance for LTS releases, but
note that it depends on community support.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
v2: fix typo in commit message
---
doc/guides/contributing/stable.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
index 8156b72b20..289769a61d 100644
--- a/doc/guides/contributing/stable.rst
+++ b/doc/guides/contributing/stable.rst
@@ -54,5 +54,6 @@ LTS Release
A stable release can be designated as an LTS release based on community
agreement and a commitment from a maintainer. The current policy is that each
-year's November (X.11) release will be maintained as an LTS for 2 years.
+year's November (X.11) release will be maintained as an LTS for 3 years,
+however that is dependent on continued community support for validation.
After the X.11 release, an LTS branch will be created for it at
--
2.43.0
next prev parent reply other threads:[~2024-01-17 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 16:18 [PATCH] " Kevin Traynor
2024-01-17 16:24 ` Kevin Traynor [this message]
2024-01-23 7:55 ` [PATCH v2] " Raslan Darawsheh
2024-03-21 14:38 ` Mcnamara, John
2024-03-24 23:14 ` Thomas Monjalon
2024-03-25 10:02 ` Morten Brørup
2024-03-28 10:01 ` Luca Boccassi
2024-03-28 10:25 ` Kevin Traynor
2024-05-23 9:12 ` Kevin Traynor
2024-05-23 9:15 ` Xueming Li
2024-06-06 9:22 ` Kevin Traynor
2024-06-20 3:54 ` 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=20240117162419.223820-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.com \
/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).