From 70f67ca90885573c669c6b7a952e89f9e0fc1e6f Mon Sep 17 00:00:00 2001 From: Joel Challis Date: Fri, 23 Dec 2022 17:53:08 +0000 Subject: [PATCH] Update breaking changes year... (#19409) --- docs/breaking_changes.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/breaking_changes.md b/docs/breaking_changes.md index 6233d5a392..586e998a1c 100644 --- a/docs/breaking_changes.md +++ b/docs/breaking_changes.md @@ -29,12 +29,12 @@ The next Breaking Change is scheduled for February 26, 2023. ### Important Dates * 2022 Nov 26 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions. -* 2022 Jan 29 - `develop` closed to new PR's. -* 2022 Jan 29 - Call for testers. -* 2022 Feb 12 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes -* 2022 Feb 19 - `develop` is locked, only critical bugfix PR's merged. -* 2022 Feb 24 - `master` is locked, no PR's merged. -* 2022 Feb 26 - Merge `develop` to `master`. +* 2023 Jan 29 - `develop` closed to new PR's. +* 2023 Jan 29 - Call for testers. +* 2023 Feb 12 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes +* 2023 Feb 19 - `develop` is locked, only critical bugfix PR's merged. +* 2023 Feb 24 - `master` is locked, no PR's merged. +* 2023 Feb 26 - Merge `develop` to `master`. * 2023 Feb 26 - `master` is unlocked. PR's can be merged again. ## What changes will be included?