Re: NVDA updates



Think of NVDA update mechanism as similar to how Chrome and Firefox updates themselves. Each NVDA branch (or a channel) is meant for different groups of users, and as such, they come with varying levels of stability:

  • Source code level: these are used by people writing new NVDA features or testing bug fixes before being reviewed by NV Access people for inclusion in NVDA.
  • Alpha (similar to Chrome/Edge Canary): this is used by developers and testers to make sure new features are working as intended and to catch bugs early. Not all features included in a given alpha build are included in final NVDA release.
  • Beta (similar to dev and beta channels for Chrome): used by early adopters and add-on authors to test upcoming features and to make add-ons compatible.
  • RC (release candidate): used to test NVDA in real-world situations in hopes of catching last-minute issues.
  • Stable: self-explanatory.


To mark a given branch as “under development”, all channels except RC and stable builds will emit a tone if an error requiring attention from users and developers occur. Also, moving from one branch to the next (particularly if moving from stable version to alpha/beta) comes with risks, including incompatible add-ons and bugs due to feature maturity.




From: <> On Behalf Of Dan Beaver
Sent: Tuesday, February 4, 2020 9:33 AM
Subject: [nvda] NVDA updates


Why does NVDA only look for updates of the type the user last installed?I am thinking of RCs and stable installs. Why not look for any and let the user decide if they want to install them or not?





Dan Beaver (KA4DAN)

Join to automatically receive all group messages.