Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Add-on Updater l10n exchange instructions from mrconfig #132

Closed
josephsl opened this issue Feb 15, 2025 · 0 comments · Fixed by #133
Closed

Remove Add-on Updater l10n exchange instructions from mrconfig #132

josephsl opened this issue Feb 15, 2025 · 0 comments · Fixed by #133

Comments

@josephsl
Copy link
Contributor

Hi,

With the introduction of NV Access add-on store in late 2023, deep maintenance mode wsa declared for Add-on Updater. This means no new features - only critical bug fixes to respond to NVDA development and exchanging localization data. The work on the add-on store continued throughout 2024, incorporating more ideas from Add-on Updater such as add-on update notification. This has accellerated in 2025 with features such as changing update URL's and changing add-on update channels, with automatic add-on update process in the work (as of February 2025).

With rapid changes to add-on store feature with features coming from Add-on Updater, it makes more sense to discontinue the add-on altogether, and as part of this, I propose terminating localization exchange for Add-on Updater from mrconfig effective March 1, 2025 (so the final localization exchange would take place on February 28, 2025). This change would close #128 - we may not konw why l10n files are placed in odd locations, but given what's happening with the add-on store, I think it woul be better to say goodbye to Add-on Updater from mrconfig.

Thanks.

seanbudd pushed a commit that referenced this issue Feb 27, 2025
Closes #132

This pull request removes Add-on Updater from localization exchange instructions - the add-on is in deep maintenance and will be discontinued soon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant