aboutsummaryrefslogtreecommitdiff
path: root/docs/breaking_changes.md
diff options
context:
space:
mode:
authorJoel Challis <[email protected]>2025-02-27 22:14:32 +0000
committerGitHub <[email protected]>2025-02-28 09:14:32 +1100
commitc4aaab5fa34ec9d66bb57c3640a5356c2daa638f (patch)
tree21fa0c16d64a0c38a64e0c14668b48858ba384da /docs/breaking_changes.md
parent1efc82403bebe759272d1ba7a79d9dfa0d5df506 (diff)
downloadqmk_firmware-c4aaab5fa34ec9d66bb57c3640a5356c2daa638f.tar.gz
qmk_firmware-c4aaab5fa34ec9d66bb57c3640a5356c2daa638f.zip
2025q1 develop changelog (#24949)
Co-authored-by: Nick Brassel <[email protected]>
Diffstat (limited to 'docs/breaking_changes.md')
-rw-r--r--docs/breaking_changes.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/breaking_changes.md b/docs/breaking_changes.md
index 132c5943cc..a5a57ccd12 100644
--- a/docs/breaking_changes.md
+++ b/docs/breaking_changes.md
@@ -10,25 +10,25 @@ Practically, this means QMK merges the `develop` branch into the `master` branch
## What has been included in past Breaking Changes?
+* [2025 Feb 23](ChangeLog/20250223)
* [2024 Nov 24](ChangeLog/20241124)
* [2024 Aug 25](ChangeLog/20240825)
-* [2024 May 26](ChangeLog/20240526)
* [Older Breaking Changes](breaking_changes_history)
## When is the next Breaking Change?
-The next Breaking Change is scheduled for February 23, 2025.
+The next Breaking Change is scheduled for May 25, 2025.
### Important Dates
-* 2024 Nov 24 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
-* 2025 Jan 26 - `develop` closed to new PRs.
-* 2025 Jan 26 - Call for testers.
-* 2025 Feb 9 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
-* 2025 Feb 16 - `develop` is locked, only critical bugfix PRs merged.
-* 2024 Nov 21 - `master` is locked, no PRs merged.
-* 2025 Feb 23 - Merge `develop` to `master`.
-* 2025 Feb 23 - `master` is unlocked. PRs can be merged again.
+* 2025 Feb 23 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
+* 2025 Apr 27 - `develop` closed to new PRs.
+* 2025 Apr 27 - Call for testers.
+* 2025 May 11 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
+* 2025 May 18 - `develop` is locked, only critical bugfix PRs merged.
+* 2025 May 23 - `master` is locked, no PRs merged.
+* 2025 May 25 - Merge `develop` to `master`.
+* 2025 May 25 - `master` is unlocked. PRs can be merged again.
## What changes will be included?