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 v3 1/2] add link in stable release section and update typical timeframe Date: Thu, 13 Jan 2022 10:19:14 +0000 Message-ID: <20220113101915.190233-1-ktraynor@redhat.com> (raw) In-Reply-To: <20220111121949.92998-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 +[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases). 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 | -- 2.31.1
next prev parent reply other threads:[~2022-01-13 10:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 12:19 [PATCH " Kevin Traynor 2022-01-11 12:19 ` [PATCH 2/2] add 21.11 LTS roadmap Kevin Traynor 2022-01-11 12:39 ` Thomas Monjalon 2022-01-11 12:43 ` [PATCH 1/2] add link in stable release section and update typical timeframe Thomas Monjalon 2022-01-11 13:22 ` Kevin Traynor 2022-01-13 10:19 ` Kevin Traynor [this message] 2022-01-13 10:19 ` [PATCH v3 2/2] add 21.11 LTS roadmap Kevin Traynor 2022-02-21 10:14 ` 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: 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=20220113101915.190233-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 \ /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
DPDK website maintenance This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/web/0 web/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 web web/ http://inbox.dpdk.org/web \ web@dpdk.org public-inbox-index web Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.web AGPL code for this site: git clone https://public-inbox.org/public-inbox.git