Where is the release commit? about adv360-pro-zmk

[ReFil]

The factory firmware is the keymap here, except with the four macro keys mapped to keycodes to facilitate testing during assembly. It is expected that customers who will be changing the default keymap will have their own uses for these four keys. There are a few different default firmwares available to download here including Dvorak: https://kinesis-ergo.com/support/kb360pro

I can understand the concern about stability, but we're always trying to improve the experience with each update

[ReFil]

The factory firmware tracks the firmware here, but has an additional commit to change the keymap. When changes are made here that change the actual firmware (e.g. not changes to the makefile or ci processes) the factory firmware gets updated.

The branch here can be considered the authoritative release branch, as we have another mechanism for development/beta testing that can be seen in the readme

[toddjonker]

Thanks for the prompt reply. I feel like I've seen a lot of churn on the GitHub issues so I have been under the impression that this repository is not particularly stable. Thus I've held off on the 3.0 update until forced into it today when my right keywell suddenly refused to connect.

I'm also curious why there's keycap changes to the factory firmware that aren't in-sync with the baseline you provide to customers that need to customize anything. (Which AFAICT includes everyone who's not on a Windows+QWERTY layout.)

[toddjonker]

Regarding the Dvorak default-firmware, I would've been happy to use such a thing, but I also need Mac mode, and the site says "These files are not customizable", so they are not helpful to me.

[ReFil]

I think i'm going to close this issue as solved now, for the avoidance of doubt we always recommend using the latest state of this repo to base any keymap customisations off of, and fetching upstream when new commits are added