Re: NVDA updates
toggle quoted messageShow quoted text
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:
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: firstname.lastname@example.org <email@example.com> 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)