forked from forks/qmk_firmware
VIA keymap deprecation notice. (#23905)
This commit is contained in:
parent
bdd10ef8e7
commit
e69d30a9e9
|
@ -109,6 +109,16 @@ Essentially, changes were made in the internals of how QMK interacts with USB fo
|
||||||
|
|
||||||
Compliance checks were run against QMK firmwares for the most popular ARM microcontrollers, as well as suspend/resume tests. As far as we can tell, a whole host of hard-to-reproduce issues are mitigated by this change.
|
Compliance checks were run against QMK firmwares for the most popular ARM microcontrollers, as well as suspend/resume tests. As far as we can tell, a whole host of hard-to-reproduce issues are mitigated by this change.
|
||||||
|
|
||||||
|
## Deprecation Notices
|
||||||
|
|
||||||
|
In line with the [notice period](support_deprecation_policy#how-much-advance-notice-will-be-given), deprecation notices for larger items are listed here.
|
||||||
|
|
||||||
|
### Migration of VIA keymaps to VIA team control
|
||||||
|
|
||||||
|
The QMK team has been in discussion with the VIA maintainers and all VIA-related keymaps in the `qmk_firmware` repository will transition to a `qmk_userspace`-style repository under the VIA team's control at the end of the next breaking changes period. This allows the VIA team to support many more custom keyboard configurations, as well as reduces the turnaround time for any changes to the VIA protocol they wish to make.
|
||||||
|
|
||||||
|
At the end of the breaking changes cycle ending 2024-08-25, VIA-enabled keymaps will no longer be accepted into the QMK repository. At the time of migration, any open PRs against `qmk_firmware` which include new VIA-related keymaps will be subsequently be asked to remove those keymaps and instead raise a PR against the userspace repository containing all VIA keymaps.
|
||||||
|
|
||||||
## Full changelist {#full-changelist}
|
## Full changelist {#full-changelist}
|
||||||
|
|
||||||
Core:
|
Core:
|
||||||
|
|
Loading…
Reference in a new issue