diff options
| author | Nick Brassel <nick@tzarc.org> | 2024-05-30 12:00:41 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-30 12:00:41 +1000 |
| commit | 6ef97172889ccd5db376b2a9f8825489e24fdac4 (patch) | |
| tree | 334e3bf41c8554d4bee73a140822f95f60eb64e9 /docs/breaking_changes.md | |
| parent | 395766657ff98a4b1fd0dcba5917557f8acbb9e4 (diff) | |
Vitepress conversion of docs. (#23795)
Diffstat (limited to 'docs/breaking_changes.md')
| -rw-r--r-- | docs/breaking_changes.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/breaking_changes.md b/docs/breaking_changes.md index 1c0b1bafce..d72a8d4761 100644 --- a/docs/breaking_changes.md +++ b/docs/breaking_changes.md | |||
| @@ -10,10 +10,10 @@ Practically, this means QMK merges the `develop` branch into the `master` branch | |||
| 10 | 10 | ||
| 11 | ## What has been included in past Breaking Changes? | 11 | ## What has been included in past Breaking Changes? |
| 12 | 12 | ||
| 13 | * [2024 May 26](ChangeLog/20240526.md) | 13 | * [2024 May 26](ChangeLog/20240526) |
| 14 | * [2024 Feb 25](ChangeLog/20240225.md) | 14 | * [2024 Feb 25](ChangeLog/20240225) |
| 15 | * [2023 Nov 26](ChangeLog/20231126.md) | 15 | * [2023 Nov 26](ChangeLog/20231126) |
| 16 | * [Older Breaking Changes](breaking_changes_history.md) | 16 | * [Older Breaking Changes](breaking_changes_history) |
| 17 | 17 | ||
| 18 | ## When is the next Breaking Change? | 18 | ## When is the next Breaking Change? |
| 19 | 19 | ||
| @@ -71,7 +71,7 @@ This section documents various processes we use when running the Breaking Change | |||
| 71 | ### 1 Week Before Merge | 71 | ### 1 Week Before Merge |
| 72 | 72 | ||
| 73 | * `develop` is now closed to PR merges, only critical bugfixes may be included | 73 | * `develop` is now closed to PR merges, only critical bugfixes may be included |
| 74 | * Announce that master will be closed from <2 Days Before> to <Day of Merge> -- message `@Breaking Changes Updates` on `#qmk_firmware` in Discord: | 74 | * Announce that master will be closed from `<2 Days Before>` to `<Day of Merge>` -- message `@Breaking Changes Updates` on `#qmk_firmware` in Discord: |
| 75 | * `@Breaking Changes Updates -- Hey folks, last day for functional PRs to be merged into qmk_firmware for this breaking changes cycle is today. After that, we're handling bugfixes only.` | 75 | * `@Breaking Changes Updates -- Hey folks, last day for functional PRs to be merged into qmk_firmware for this breaking changes cycle is today. After that, we're handling bugfixes only.` |
| 76 | 76 | ||
| 77 | ### 2 Days Before Merge | 77 | ### 2 Days Before Merge |
| @@ -136,7 +136,7 @@ This happens immediately after the previous `develop` branch is merged to `maste | |||
| 136 | * Announce that both `master` and `develop` are now unlocked -- message `@Breaking Changes Updates` on `#qmk_firmware` in Discord: | 136 | * Announce that both `master` and `develop` are now unlocked -- message `@Breaking Changes Updates` on `#qmk_firmware` in Discord: |
| 137 | * `@Breaking Changes Updates -- Hey folks, develop has now been merged into master -- newest batch of changes are now available for everyone to use!` | 137 | * `@Breaking Changes Updates -- Hey folks, develop has now been merged into master -- newest batch of changes are now available for everyone to use!` |
| 138 | 138 | ||
| 139 | * (Optional) [update ChibiOS + ChibiOS-Contrib on `develop`](chibios_upgrade_instructions.md) | 139 | * (Optional) [update ChibiOS + ChibiOS-Contrib on `develop`](chibios_upgrade_instructions) |
| 140 | 140 | ||
| 141 | 141 | ||
| 142 | ### Set up Discord events for the next cycle | 142 | ### Set up Discord events for the next cycle |