DPDK website maintenance
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: web@dpdk.org
Cc: bluca@debian.org, christian.ehrhardt@canonical.com,
	xuemingl@nvidia.com, thomas@monjalon.net, ferruh.yigit@intel.com,
	david.marchand@redhat.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [PATCH v2 1/2] add link in stable release section and update typical timeframe
Date: Thu, 13 Jan 2022 10:11:55 +0000	[thread overview]
Message-ID: <20220113101156.189859-1-ktraynor@redhat.com> (raw)
In-Reply-To: <20211213164858.74244-1-ktraynor@redhat.com>

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
 content/roadmap/_index.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 9d3f8e6..cf212a4 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -129,4 +129,6 @@ backported by the stable maintainers into the respective branches in "bursts".
 Developers can provide stable-specific patches by sending them
 to stable@dpdk.org only (avoiding dev@dpdk.org).
+Further information on subject prefixes for this case is documented
 After all the relevant bugfixes have been backported,
@@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced.
 Typically a new stable release version follows a mainline release
-by 1-2 weeks, depending on the test results.
+by 3-6 weeks, depending on the test results.
 | Current version | Next version | Next version Date | End of life | Maintainers            |

       reply	other threads:[~2022-01-13 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211213164858.74244-1-ktraynor@redhat.com>
2022-01-13 10:11 ` Kevin Traynor [this message]
2022-01-13 10:11   ` [PATCH v2 2/2] add 21.11 LTS roadmap Kevin Traynor
2022-01-13 11:17     ` Mcnamara, John
2022-01-13 10:13   ` [PATCH v2 1/2] add link in stable release section and update typical timeframe Kevin Traynor

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=20220113101156.189859-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    --cc=xuemingl@nvidia.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).