Updated dates, larger examples for key overrides change.
This commit is contained in:
parent
c31f2fdb4c
commit
10d5802fa8
2 changed files with 16 additions and 9 deletions
|
|
@ -36,12 +36,19 @@ If you're using key overrides, in your `keymap.c` will need to change the signat
|
|||
|
||||
```c
|
||||
const key_override_t **key_overrides = (const key_override_t *[]){
|
||||
&my_override_1,
|
||||
&my_override_2,
|
||||
NULL
|
||||
};
|
||||
```
|
||||
|
||||
to:
|
||||
|
||||
```c
|
||||
const key_override_t *key_overrides[] = {
|
||||
&my_override_1,
|
||||
&my_override_2,
|
||||
};
|
||||
```
|
||||
|
||||
The list of key overrides now does not need to be `NULL`-terminated.
|
||||
|
|
|
|||
|
|
@ -21,14 +21,14 @@ The next Breaking Change is scheduled for August 25, 2024.
|
|||
|
||||
### Important Dates
|
||||
|
||||
* 2024 May 26 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
|
||||
* 2024 Jul 28 - `develop` closed to new PRs.
|
||||
* 2024 Jul 28 - Call for testers.
|
||||
* 2024 Aug 4 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
|
||||
* 2024 Aug 18 - `develop` is locked, only critical bugfix PRs merged.
|
||||
* 2024 Aug 22 - `master` is locked, no PRs merged.
|
||||
* 2024 Aug 25 - Merge `develop` to `master`.
|
||||
* 2024 Aug 25 - `master` is unlocked. PRs can be merged again.
|
||||
* 2024 Aug 25 - `develop` is tagged with a new release version. Each push to `master` is subsequently merged to `develop` by GitHub actions.
|
||||
* 2024 Oct 27 - `develop` closed to new PRs.
|
||||
* 2024 Oct 27 - Call for testers.
|
||||
* 2024 Nov 10 - Last day for merges -- after this point `develop` is locked for testing and accepts only bugfixes
|
||||
* 2024 Nov 17 - `develop` is locked, only critical bugfix PRs merged.
|
||||
* 2024 Nov 22 - `master` is locked, no PRs merged.
|
||||
* 2024 Nov 24 - Merge `develop` to `master`.
|
||||
* 2024 Nov 24 - `master` is unlocked. PRs can be merged again.
|
||||
|
||||
## What changes will be included?
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ Criteria for acceptance:
|
|||
|
||||
Strongly suggested:
|
||||
|
||||
* The PR has a ChangeLog file describing the changes under `<qmk_firmware>/docs/Changelog/20240526`.
|
||||
* The PR has a ChangeLog file describing the changes under `<qmk_firmware>/docs/Changelog/20241124`.
|
||||
* This should be in Markdown format, with a name in the format `PR12345.md`, substituting the digits for your PRs ID.
|
||||
* One strong recommendation that the ChangeLog document matches the PR description on GitHub, so as to ensure traceability.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue