instal the new for windows NVDA 2023.2 Beta 2

The fact that API breaking changes are planned for a 20XY.1 release is only due to current process. This alludes to a concept that doesn't exist elsewhere, EG that all the 2021 releases are somewhat related. I wish we were alerted to the messaging problem earlier, but at least I'm glad that we have a record of this for posterity. I remember the add-ons community going through a massive confusion in early 2019 when version compatibility flags were first introduced.

Anything that's concise, easy to translate, and communicates the reason clearly.The last tested NVDA version (lastTestedVersion) is older than currentNVDAVersion.

Last tested version: lastTestedVersion, add-on must be compatible with currentNVDAVersion.

addonName is incompatible with the version of NVDA you are using.

In addition to the proposed message, others can include (addonName is the name of the add-on being installed):

This message will be translated into many languages, so let us make it concise while providing needed information.

Further, the messaging implies people know about the backward compatibility policy, something newbiews are not even aware of unless told otherwise.

As Luke and Brian point out, the current messaging does not say the latest compatible NVDA version for an add-on.

I advise a careful consideration of the messaging here because: Note that UI string changes are not accepted for 2022.1, but I think we might as well take care of this in 2022.2. Actualy, CC, , and other add-ons community members

Instal the new for windows NVDA 2023.2 Beta 2