From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [PATCH v2] update 2022 schedule
Date: Mon, 13 Dec 2021 11:54:24 +0100 [thread overview]
Message-ID: <20211213105424.65258-1-thomas@monjalon.net> (raw)
In-Reply-To: <5774339.lOV4Wx5bFT@thomas>
22.03 is planned to be a small release cycle.
Given December is a calm month,
the proposal deadline and -rc1 are pushed by one week.
For the rest of the schedule, this guideline (in weeks) is followed:
proposal deadline: 4
rc1 - API freeze: 7
rc2 - PMD features freeze: 3
rc3 - app features freeze: 1
rc4 - more fixes: 1
rc5 - last chance buffer: 1
release: 0.5
This is a new pace of 3 releases per year, instead of 4 previously.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: John McNamara <john.mcnamara@intel.com>
---
v2: adapt cycle description to the new pace while merging the patch
---
content/roadmap/_index.md | 28 ++++++++++++++++++++++------
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 069c5c4..9c41991 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -52,7 +52,7 @@ This list is obviously neither complete nor guaranteed.
### Cycle model {#cycle}
----
-A typical release should be done after 3 months.
+A typical release should be done after 4 months.
It is designed to allow DPDK to keep evolving at a rapid pace while
giving enough opportunity to review, discuss and improve the contributions.
@@ -65,20 +65,36 @@ Updated versions of patches (v2, v3, etc.) will be submitted to address comments
The new features must be properly reviewed, tested and accepted before the
integration deadline. Otherwise, they will be postponed to the next releases.
-At the end of the merge window, the first release candidate is out.
+At the end of the merge windows, the first release candidates are out.
-The last period is 1 month long and is dedicated to bug fixing.
+The last period is approximately 1 month long and is dedicated to bug fixing.
### Scheduling {#dates}
----
#### 22.03
-- Proposal deadline (RFC/v1 patches): 24 December 2021
-- API freeze (-rc1): 2 February 2022
+- Proposal deadline (RFC/v1 patches): 31 December 2021
+- API freeze (-rc1): 9 February 2022
- PMD features freeze (-rc2): 23 February 2022
- Builtin applications features freeze (-rc3): 2 March 2022
-- Release: early March 2022
+- Release: 11 March 2022
+
+#### 22.07
+
+- Proposal deadline (RFC/v1 patches): 10 April 2022
+- API freeze (-rc1): 30 May 2022
+- PMD features freeze (-rc2): 20 June 2022
+- Builtin applications features freeze (-rc3): 27 June 2022
+- Release: 13 July 2022
+
+#### 22.11
+
+- Proposal deadline (RFC/v1 patches): 14 August 2022
+- API freeze (-rc1): 3 October 2022
+- PMD features freeze (-rc2): 24 October 2022
+- Builtin applications features freeze (-rc3): 31 October 2022
+- Release: 16 November 2022
### Stable Releases {#stable}
----
--
2.34.1
prev parent reply other threads:[~2021-12-13 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 9:58 [PATCH] " Thomas Monjalon
2021-12-13 10:20 ` Mcnamara, John
2021-12-13 10:24 ` Thomas Monjalon
2021-12-13 10:54 ` Thomas Monjalon [this message]
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=20211213105424.65258-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=john.mcnamara@intel.com \
--cc=web@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).