v2.23-rc2

[Ralim]

This is a release candidate, this will be promoted to a full release depending on how many issues are found 😓

This builds on RC1

High level changes since RC1

1. Fixes to the ID numbers used for operating modes over BLE
2. Rework of the I2C on PinecilV2 to remove issues with temperature regulation and screen glitching
3. Default for USB-PD negotiation changed to use "safe" profile, to be conservative in selecting voltages.
4. Fixes for USB-PD to implement device caps. This should fix unit reboot issues with some laptops
5. Looots of translation & documentation updates ❤️

What's Changed since RC1 (All)

• Typo corrected (Squire -> Sequre) by @StevenSeifried in Typo corrected (Squire -> Sequre) #2028
• Updated translation_DE.json by @StevenSeifried in Updated translation_DE.json #2029
• Updated translation_DE.json (again) by @StevenSeifried in Updated translation_DE.json (again) #2030
• Add macro to enable tip types for supported hardware only by @ia in Add macro to enable tip types for supported hardware only #2031
• Set tip type as auto by default in runtime by @ia in Set tip type as auto by default in runtime #2032
• Update PL translation (v2.23 rc1) by @KITT3000 in Update PL translation (v2.23 rc1) #2035
• Allocate fixed ID's for Operating Modes by @Ralim in Allocate fixed ID's for Operating Modes #2042
• Update translation_IT.json by @fredericuslaurentii in Update translation_IT.json #2052
• Update translation_UK.json by @resistancelion in Update translation_UK.json #2058
• scripts/deploy.sh: add handmade linter for translation-related json files to check for tabs and odd spaces by @ia in scripts/deploy.sh: add handmade linter for translation-related json files to check for tabs and odd spaces #2064
• refactor(core/settingsgui): code cleaning by @safocl in refactor(core/settingsgui): code cleaning #2065
• fix: accessing inactive union members by @safocl in fix: accessing inactive union members #2066
• README.md: add notice about BLE turned off by default now by @ia in README.md: add notice about BLE turned off by default now #2067
• README.md: fix formatting of heading levels for BLE section by @ia in README.md: fix formatting of heading levels for BLE section #2068
• Added guide for compiling under Windows by @resistancelion in Added guide for compiling under Windows #2060
• Default to no EPR/PPS so its opt in by @Ralim in Default to no EPR/PPS so its opt in #2073
• Add the notice about EPR/PPS disabled by default in the main README.md by @ia in Add the notice about EPR/PPS disabled by default in the main README.md #2074
• Debug Menu: add time of compilation to timestamp build by @ia in Debug Menu: add time of compilation to timestamp build #2075
• USB-PD: Add minimal sink caps by @Ralim in USB-PD: Add minimal sink caps #2081
• Fix: Potential Vulnerability in Cloned Function by @tabudz in Fix: Potential Vulnerability in Cloned Function #2083
• Dont adjust pinecilv2 max temp by Coe by @Ralim in Dont adjust pinecilv2 max temp by Coe #2082
• Updated Overall French Translations by @JustLeska in Updated Overall French Translations #2085
• Fixed & Updated French Translations by @JustLeska in Fixed & Updated French Translations #2086
• Rev2 reworking I2C to avoid IRQ stalling && adjusting thermal runaway for PinecilV2 by @Ralim in Rev2 reworking I2C to avoid IRQ stalling && adjusting thermal runaway for PinecilV2 #2049

New Contributors

• @resistancelion made their first contribution in Update translation_UK.json #2058
• @safocl made their first contribution in refactor(core/settingsgui): code cleaning #2065
• @tabudz made their first contribution in Fix: Potential Vulnerability in Cloned Function #2083
• @JustLeska made their first contribution in Updated Overall French Translations #2085

Full Changelog: v2.23-rc1...v2.23-rc2

---

This discussion was created from the release v2.23-rc2.

[ia]

@Ralim, I would like to ask you one very specific favor about "release management", if possible (there is v2.23-rc3 already, but there is no discussion page for that, so I'm writing here): could you, please, make a "three days notice" here to me in the comments before tagging the next rc and/or release? So I could better plan my own work about with what I should hurry to submit before release, and what could wait for the next release. I hope you understand. Thanks. :)

TL;DR: every rc/release is a big surprise for me as much as for users, but I would like to have it a bit more transparent with early notice, to plan my own work for upcoming/next release. :D

[Ralim]

The loose plan is roughly:

Generally RC's start to come once the Milestone list gets fairly empty for that release.

In terms of releases I try to get one major thing in each release at the minimum (so no small releases that contain one thing). But large depends on my available time.

One I start tagging RC's I'm mostly focused on burning down any new bugs, and other new things should really wait to the next release. I don't stick hard and fast by this if its a small feature that is reasonably easy to test (i.e. I can cover all the test cases in < 10 minutes).

I find I cant stick to exact monthly or quarterly cadence often due to life getting busy and quiet semi-randomly. Which raises the problem of if I'm available to do work to move things on, generally I want to do another clean-up pass and rc then, as I don't know if the next time I'll be available will be tomorrow or the next week.

I'm happy to look at a newer process but I've generally just been using the Milestone feature to mark when I'm roughly planning to get stuff done by? 😓

Note: I stopped making the automatic discussion as people didn't really use them and instead just opened issues so that felt more the community vibe 😓

[ia]

Dear @Ralim, thank you a lot for finding the time for this very detailed reply about your release management. :)
But if it won't be too much for me to ask, my humble inquiry remains, so if you have time & mood, every time you decide that it's release [candidate] time, I just would like to be aware a bit of ahead, like T-3 days or so. 🙏