|
Hi, I expect the store won’t be ready in time for 2023.1. At the moment my plan is to discontinue Add-on Updater at least one release after the store makes its debut. For example, if the add-on store is indeed included in NVDA 2023.2 (unlikely but possible), then Add-on Updater will be discontinued shortly after 2023.3 is released. This is so that we can transition to using the add-on store, including Add-on Updater for folks using older NVDA releases for a while (although it will not be documented, things are put in place in Add-on Updater to switch to NV Access add-on store to access update information once NV Access declares the store ready for add-on submissions). Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Rowen Cary Sent: Tuesday, January 17, 2023 7:47 AM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi, Joseph, Thanks for all your hard work. Thank you for all you bring to the NVDA community. The add-on store has been on the topic for several years, and as Cyrille said, I really don't have the confidence to see it in the next few releases. Thanks
|
|
|
Hi, Joseph,
Thanks for all your hard work. Thank you for all you bring to the NVDA community.
The add-on store has been on the topic for several years, and as Cyrille said, I really don't have the confidence to see it in the next few releases.
Thanks
|
|
|
Hi
Yes, I have seen the PR. But the PR is from Reef who has left. There are also other PRs that are opened during years and finally abandoned for any reason. Also the add-on store has been announced many times around 2020 but is not yet a merged reality. So I guess that I am waiting to see add-on store merged in alpha branch before I'll really believe to it as a replacement.
Also, sorry for having wrongly included add-on updater in the list of extensions calling for a new maintener!
Cheers,
Cyrille
toggle quoted message
Show quoted text
On Tue, Jan 17, 2023 at 11:31 AM, Joseph Lee wrote:
Hi,
There is a branch in NVDA Core source code that does bring a minimal store to reality, and work on the store itself (a series of GitHub repos) is making progress.
As for the call for maintainers, Add-on Updater isn’t on the list.
Cheers,
Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Tuesday, January 17, 2023 1:34 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time
Hi Joseph
IMO it may still be useful to report the issue today.
I understand that you have decided to make only minimal maintenance for the add-on and we all respect this choice. But you do not know the future. The add-on store has been announced now for at least 3 years and we do not know when it will become a reality. In the meantime, addonUpdater fulfills the need of many users. I know that you have called many times without so much success (unfortunately), but maybe someone will finally offer to help to maintain add-on updater.
Again, it's just my opinion and the decision is finally yours in any case. Whichever it will be, thanks for all your hard work.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 09:53 PM, Joseph Lee wrote:
Hi,
It would have made sense to open an issue on mrconfig repo in say, 2021 or early 2022. At this stage, with Add-on Updater moving to maintenance mode soon, I figured it would not make much sense to do so. This does not mean I don’t care about localization data for this add-on.
Cheers,
Joseph
Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote:
Hi,
Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued.
Cheers,
Joseph
There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi, There is a branch in NVDA Core source code that does bring a minimal store to reality, and work on the store itself (a series of GitHub repos) is making progress. As for the call for maintainers, Add-on Updater isn’t on the list. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io Sent: Tuesday, January 17, 2023 1:34 AM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi Joseph
IMO it may still be useful to report the issue today.
I understand that you have decided to make only minimal maintenance for the add-on and we all respect this choice. But you do not know the future. The add-on store has been announced now for at least 3 years and we do not know when it will become a reality. In the meantime, addonUpdater fulfills the need of many users. I know that you have called many times without so much success (unfortunately), but maybe someone will finally offer to help to maintain add-on updater.
Again, it's just my opinion and the decision is finally yours in any case. Whichever it will be, thanks for all your hard work.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 09:53 PM, Joseph Lee wrote: Hi, It would have made sense to open an issue on mrconfig repo in say, 2021 or early 2022. At this stage, with Add-on Updater moving to maintenance mode soon, I figured it would not make much sense to do so. This does not mean I don’t care about localization data for this add-on. Cheers, Joseph Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote: Hi, Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued. Cheers, Joseph There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi Joseph
IMO it may still be useful to report the issue today.
I understand that you have decided to make only minimal maintenance for the add-on and we all respect this choice. But you do not know the future. The add-on store has been announced now for at least 3 years and we do not know when it will become a reality. In the meantime, addonUpdater fulfills the need of many users. I know that you have called many times without so much success (unfortunately), but maybe someone will finally offer to help to maintain add-on updater.
Again, it's just my opinion and the decision is finally yours in any case. Whichever it will be, thanks for all your hard work.
Cheers,
Cyrille
toggle quoted message
Show quoted text
On Mon, Jan 16, 2023 at 09:53 PM, Joseph Lee wrote:
Hi,
It would have made sense to open an issue on mrconfig repo in say, 2021 or early 2022. At this stage, with Add-on Updater moving to maintenance mode soon, I figured it would not make much sense to do so. This does not mean I don’t care about localization data for this add-on.
Cheers,
Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Monday, January 16, 2023 12:43 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time
Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote:
Hi,
Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued.
Cheers,
Joseph
There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi, The biggest reason for this decision is that Add-on Updater is never meant to stay with us forever – the add-on is based on an NVDA pull request, and when I released the first version in 2018, I did state that the add-on will be discontinued once NVDA issue 3208 (ability to check for, download, and update add-ons) is resolved. While the implementation is different, the NV Access add-on store fulfills the requirement for discontinuing Ad-on Updater once included with NVDA. As NV Access has been working on the store for a while, I decided to focus more on internals rather than adding new features and changes and wait for the add-on store code to be developed further – this is why the upcoming Add-on Updater release will align more closely with the add-on store both to prepare for the store and to communicate to people that the store is the successor of Add-on Updater. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Rowen Cary Sent: Monday, January 16, 2023 10:31 PM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time hi, Joseph, Although you have the final say, I still can't understand why the problem with the localization system is refused to be fixed until the add-on goes into maintenance mode, going into maintenance mode does not mean that the plugin itself can have bugs.
|
|
|
hi, Joseph,
Although you have the final say, I still can't understand why the problem with the localization system is refused to be fixed until the add-on goes into maintenance mode, going into maintenance mode does not mean that the plugin itself can have bugs.
|
|
|
Imo, if a project is moving to maintaining mode, is better that the translation system is fixed before it, but of course the decision is yours. I think that many people would like NV Access to move forward the add-on store if they want to offer a service to store and update add-ons. Hope they can say something about this, related to add-on updater since this may make it to be discontinued. Now that Reef has left NV Access, maybe good to know the situation for the store, since he was one of the developers who worked on it. We may open a different thread or a GitHub discusion to ask directly to them. If someone wants to do it, perfect. Otherwise I"ll do it when I go back to home from hollidays. Enviado desde mi iPhone
El 16 ene 2023, a las 21:53, Joseph Lee <joseph.lee22590@...> escribió:
Hi, It would have made sense to open an issue on mrconfig repo in say, 2021 or early 2022. At this stage, with Add-on Updater moving to maintenance mode soon, I figured it would not make much sense to do so. This does not mean I don’t care about localization data for this add-on. Cheers, Joseph From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Monday, January 16, 2023 12:43 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote: Hi, Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued. Cheers, Joseph There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi, It would have made sense to open an issue on mrconfig repo in say, 2021 or early 2022. At this stage, with Add-on Updater moving to maintenance mode soon, I figured it would not make much sense to do so. This does not mean I don’t care about localization data for this add-on. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io Sent: Monday, January 16, 2023 12:43 PM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote: Hi, Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued. Cheers, Joseph There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi Joseph
IMO, if you want to get more chance for this issue to be fixed, you should report it opening an issue against mrconfig. I had already made this suggestion in the past but you did not seem interested.
Fixing issues in mrconfig is not high priority for NVAccess and they do not work so often on this repo. But if the issue is not reported to them, you can be sure that it will never be fixed. In these days, Sean has been working in this repo so this may be a good time to open the issue. Sometimes, the translation framework is just blocked by merge conflicts on the files.
Just my opinion though, I hope you do not mind.
Cheers,
Cyrille
toggle quoted message
Show quoted text
On Mon, Jan 16, 2023 at 07:51 PM, Joseph Lee wrote:
Hi,
Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued.
Cheers,
Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Rowen Cary
Sent: Monday, January 16, 2023 10:34 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time
There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi, Unfortunately, this cannot be done – this requires looking at mrconfig to figure out why Add-on Updater localization data is not picked up (docs) or placed somewhere else (po files). As it stands, I expect it won’t be fixed until Add-on Updater is discontinued. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Rowen Cary Sent: Monday, January 16, 2023 10:34 AM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
There is a problem that AddonUpdater's documentation translation keeps not getting updated. Would you consider updating it in an upcoming release?
|
|
|
Hi all,
An importatn update on 23.02 release date: at the moment tentative release date for 23.02 releases is February 3, 2023, but that can change if NVDA 2023.1 beta 1 is released before then - if that hapens, 23.02 add-on updates will be released within 24 hours of NVDA 2023.1 beta 1 release. If NVDA 2023.1 beta 1 does come out in February after 23.02 add-on updates are released, I will release compatibility updates and will push final add-on releases (for end of life add-ons) to a later date. At least a week after final add-on updates come out, I will send a notice to this list, declaring end of life add-ons as legacy on community add-ons website and providing add-on soruce code repositories.
Cheers,
Jsoeph
|
|
|
It's a pity, I'm very interested in Office desks.
|
|
|
Thanks Joseph and Brian. Feel really silly now. Doesn't seem like
two minutes ago since the only way of recovering from such a
problem was by a good old CD and formatting your drive and so on.
Someone really needs to boot me into the 21st century haha.
Cheers.
On 03/01/2023 16:35, Joseph Lee wrote:
toggle quoted message
Show quoted text
Hi,
Add-ons will not even install on older
Windows releases.
As for the issue you’ve got with Windows 10
21H1, I advise using Media Creation Tool to upgrade to 22H2.
Cheers,
Joseph
Hi,
What will happen to those of us stuck on older Windows
releases for whatever reason? My Windows errors when updating
meaning I can't go beyond 21H1 at the moment. Will my addons
come up on Addon Updater and then refuse to work? Or will they
just not update?
Incidentally, if you have any ideas as to why my Windows
might be having a fit, I'd be really grateful for any tips
there as well.
Cheers.
On 03/01/2023 16:17, Joseph Lee wrote:
Hi,
Two more things:
- For
add-ons going out of support, I’m no longer accepting new
issues/pull requests/feature suggestions/change requests
i.e. features and code are frozen.
2. Add-on
Updater: while not really marked as such, Add-on Updater
will enter maintenance mode, starting with 23.02 release
provided that progress is made to NV Access add-on store
proposal. The last two features of Add-on Updater will be
supporting and switching to the new add-on store
infrastructure and deactivating the add-on altogether once
NVDA comes with its own add-on updating/store mechanism.
Cheers,
Joseph
Hi all,
Three important notices and a call:
- Notice 1:
version 23.02 of my add-ons will require NVDA 2022.4 or
later.
- Notice 2:
February releases of my add-ons (except Add-on Updater)
will require Windows 10 21H2 or later (slightly relaxed
from 22H2 requirement to support enterprises).
- Notice 3:
apart from two or three add-ons, version 23.02 will be the
second to last releases from me.
Some of you may remember a post from me
last year calling on the community to maintain my add-ons
I’m no longer maintaining (Enhanced Touch Gestures, Event
Tracker, GoldWave, Object Location Tones, ObjPad, Resource
Monitor, Sound Splitter, StationPlaylist). I did promise
that if no-one shows up to maintain these add-ons, I will
come back and update them in late 2022, which is exactly
what I did for the last few days. But now I must ask you,
one final time: please keep these add-ons going by finding
new maintainers, and now, I’m adding Office Desk to the mix.
I’m calling upon the community for
maintainers one last time as I have no development plans for
the listed add-ons after early 2023. The very last releases
from me will be to make these add-ons compatible with NVDA
2023.1, and that can happen at any moment. Because I did say
that February releases will require NVDA 2022.4, I am
committing to that.
In addition, as I noted a few days ago,
future add-on releases will require newer Windows 10
releases or later, and that time has come: February add-on
releases will indeed require Windows 10 Version 21H2
(November 2021 Update) or later. Originally I said 22H2, but
to give enterprises time to migrate to newer Windows
releases, I decided to support 21H2 in the time being.
Besides, Windows 10 21H2 is the latest long-term servicing
release for specialized devices.
The reason for asking you to use newer
Windows releases in February is to reduce uncertainty. As
NVDA 2023.1 beta 1 can be released anytime, it wouldn’t make
sense to dedicate an add-on release solely for Windows
release requirements at this stage. Besides, this change
reflects the fact that I really do not have any plans for
the listed add-ons after February apart from compatibility
update.
One thing that’s going to be different
from 2022: whereas I did say in 2022 that I will come back
to update add-ons if no-one shows up to maintain them, I
won’t do so in 2023 for an important reason: reducing NVDA
community workload. If things go as planned, the only
add-ons I will be maintaining after February 2023 will be
Add-on Updater and Windows App Essentials; I wanted to keep
Office Desk going and help coordinate its development, but
looks like there aren’t that many people interested in
developing this add-on. Even for Windows App Essentials, the
future of this add-on is uncertain at the moment, as that’s
the only add-on left in my lab once Add-on Updater is
discontinued when NVDA itself starts checking for add-on
updates.
In summary:
- February
2023 releases will be the second to last (true) releases
of the following add-ons from me: Enhanced Touch Gestures,
Event Tracker, GoldWave, Object Location Tones, ObjPad,
Office Desk, Resource Monitor, Sound Splitter,
StationPlaylist. These releases will require NVDA 2022.4
or later and Windows 10 21H2 or later.
- The very
last releases of these add-ons will be a compatibility
update for NVDA 2023.1. Shortly after, these add-ons will
be marked as “legacy” in community add-ons website, and I
will give you at least 30 days notice before declaring
them end of life.
Cheers,
Joseph
|
|
|
On Tue, Jan 3, 2023 at 11:35 AM, Joseph Lee wrote:
I advise using Media Creation Tool to upgrade to 22H2.
- A closely allied method which often works when all else fails: Performing a Windows 10 or 11 Repair Install or Feature Update Using the Windows ISO file
When a machine has been really cranky about updating, I prefer to do the above method with the machine entirely offline, as all components necessary for the basic upgrade are contained in the ISO file. Windows Update will take care of fetching any patch-type updates that may have been made after the ISO (or the components used to build it, in the case of Windows 10) had been created by Microsoft. -- Brian - Windows 10, 64-Bit, Version 21H2, Build 19044
Any idiot can face a crisis. It's the day-to-day living that wears you out.
~ Anton Chekhov
|
|
|
Hi, Add-ons will not even install on older Windows releases. As for the issue you’ve got with Windows 10 21H1, I advise using Media Creation Tool to upgrade to 22H2. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Day Garwood Sent: Tuesday, January 3, 2023 8:23 AM To: nvda-addons@nvda-addons.groups.io Subject: Re: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi, What will happen to those of us stuck on older Windows releases for whatever reason? My Windows errors when updating meaning I can't go beyond 21H1 at the moment. Will my addons come up on Addon Updater and then refuse to work? Or will they just not update? Incidentally, if you have any ideas as to why my Windows might be having a fit, I'd be really grateful for any tips there as well. Cheers. On 03/01/2023 16:17, Joseph Lee wrote: Hi, Two more things: - For add-ons going out of support, I’m no longer accepting new issues/pull requests/feature suggestions/change requests i.e. features and code are frozen.
2. Add-on Updater: while not really marked as such, Add-on Updater will enter maintenance mode, starting with 23.02 release provided that progress is made to NV Access add-on store proposal. The last two features of Add-on Updater will be supporting and switching to the new add-on store infrastructure and deactivating the add-on altogether once NVDA comes with its own add-on updating/store mechanism. Cheers, Joseph Hi all, Three important notices and a call: - Notice 1: version 23.02 of my add-ons will require NVDA 2022.4 or later.
- Notice 2: February releases of my add-ons (except Add-on Updater) will require Windows 10 21H2 or later (slightly relaxed from 22H2 requirement to support enterprises).
- Notice 3: apart from two or three add-ons, version 23.02 will be the second to last releases from me.
Some of you may remember a post from me last year calling on the community to maintain my add-ons I’m no longer maintaining (Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Resource Monitor, Sound Splitter, StationPlaylist). I did promise that if no-one shows up to maintain these add-ons, I will come back and update them in late 2022, which is exactly what I did for the last few days. But now I must ask you, one final time: please keep these add-ons going by finding new maintainers, and now, I’m adding Office Desk to the mix. I’m calling upon the community for maintainers one last time as I have no development plans for the listed add-ons after early 2023. The very last releases from me will be to make these add-ons compatible with NVDA 2023.1, and that can happen at any moment. Because I did say that February releases will require NVDA 2022.4, I am committing to that. In addition, as I noted a few days ago, future add-on releases will require newer Windows 10 releases or later, and that time has come: February add-on releases will indeed require Windows 10 Version 21H2 (November 2021 Update) or later. Originally I said 22H2, but to give enterprises time to migrate to newer Windows releases, I decided to support 21H2 in the time being. Besides, Windows 10 21H2 is the latest long-term servicing release for specialized devices. The reason for asking you to use newer Windows releases in February is to reduce uncertainty. As NVDA 2023.1 beta 1 can be released anytime, it wouldn’t make sense to dedicate an add-on release solely for Windows release requirements at this stage. Besides, this change reflects the fact that I really do not have any plans for the listed add-ons after February apart from compatibility update. One thing that’s going to be different from 2022: whereas I did say in 2022 that I will come back to update add-ons if no-one shows up to maintain them, I won’t do so in 2023 for an important reason: reducing NVDA community workload. If things go as planned, the only add-ons I will be maintaining after February 2023 will be Add-on Updater and Windows App Essentials; I wanted to keep Office Desk going and help coordinate its development, but looks like there aren’t that many people interested in developing this add-on. Even for Windows App Essentials, the future of this add-on is uncertain at the moment, as that’s the only add-on left in my lab once Add-on Updater is discontinued when NVDA itself starts checking for add-on updates. In summary: - February 2023 releases will be the second to last (true) releases of the following add-ons from me: Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Office Desk, Resource Monitor, Sound Splitter, StationPlaylist. These releases will require NVDA 2022.4 or later and Windows 10 21H2 or later.
- The very last releases of these add-ons will be a compatibility update for NVDA 2023.1. Shortly after, these add-ons will be marked as “legacy” in community add-ons website, and I will give you at least 30 days notice before declaring them end of life.
Cheers, Joseph
|
|
|
Hi,
What will happen to those of us stuck on older Windows releases
for whatever reason? My Windows errors when updating meaning I
can't go beyond 21H1 at the moment. Will my addons come up on
Addon Updater and then refuse to work? Or will they just not
update?
Incidentally, if you have any ideas as to why my Windows might be
having a fit, I'd be really grateful for any tips there as well.
Cheers.
On 03/01/2023 16:17, Joseph Lee wrote:
toggle quoted message
Show quoted text
Hi,
Two more things:
- For add-ons
going out of support, I’m no longer accepting new
issues/pull requests/feature suggestions/change requests
i.e. features and code are frozen.
2. Add-on
Updater: while not really marked as such, Add-on Updater will
enter maintenance mode, starting with 23.02 release provided
that progress is made to NV Access add-on store proposal. The
last two features of Add-on Updater will be supporting and
switching to the new add-on store infrastructure and
deactivating the add-on altogether once NVDA comes with its
own add-on updating/store mechanism.
Cheers,
Joseph
Hi all,
Three important notices and a call:
- Notice 1:
version 23.02 of my add-ons will require NVDA 2022.4 or
later.
- Notice 2:
February releases of my add-ons (except Add-on Updater) will
require Windows 10 21H2 or later (slightly relaxed from 22H2
requirement to support enterprises).
- Notice 3:
apart from two or three add-ons, version 23.02 will be the
second to last releases from me.
Some of you may remember a post from me
last year calling on the community to maintain my add-ons I’m
no longer maintaining (Enhanced Touch Gestures, Event Tracker,
GoldWave, Object Location Tones, ObjPad, Resource Monitor,
Sound Splitter, StationPlaylist). I did promise that if no-one
shows up to maintain these add-ons, I will come back and
update them in late 2022, which is exactly what I did for the
last few days. But now I must ask you, one final time: please
keep these add-ons going by finding new maintainers, and now,
I’m adding Office Desk to the mix.
I’m calling upon the community for
maintainers one last time as I have no development plans for
the listed add-ons after early 2023. The very last releases
from me will be to make these add-ons compatible with NVDA
2023.1, and that can happen at any moment. Because I did say
that February releases will require NVDA 2022.4, I am
committing to that.
In addition, as I noted a few days ago,
future add-on releases will require newer Windows 10 releases
or later, and that time has come: February add-on releases
will indeed require Windows 10 Version 21H2 (November 2021
Update) or later. Originally I said 22H2, but to give
enterprises time to migrate to newer Windows releases, I
decided to support 21H2 in the time being. Besides, Windows 10
21H2 is the latest long-term servicing release for specialized
devices.
The reason for asking you to use newer
Windows releases in February is to reduce uncertainty. As NVDA
2023.1 beta 1 can be released anytime, it wouldn’t make sense
to dedicate an add-on release solely for Windows release
requirements at this stage. Besides, this change reflects the
fact that I really do not have any plans for the listed
add-ons after February apart from compatibility update.
One thing that’s going to be different from
2022: whereas I did say in 2022 that I will come back to
update add-ons if no-one shows up to maintain them, I won’t do
so in 2023 for an important reason: reducing NVDA community
workload. If things go as planned, the only add-ons I will be
maintaining after February 2023 will be Add-on Updater and
Windows App Essentials; I wanted to keep Office Desk going and
help coordinate its development, but looks like there aren’t
that many people interested in developing this add-on. Even
for Windows App Essentials, the future of this add-on is
uncertain at the moment, as that’s the only add-on left in my
lab once Add-on Updater is discontinued when NVDA itself
starts checking for add-on updates.
In summary:
- February
2023 releases will be the second to last (true) releases of
the following add-ons from me: Enhanced Touch Gestures,
Event Tracker, GoldWave, Object Location Tones, ObjPad,
Office Desk, Resource Monitor, Sound Splitter,
StationPlaylist. These releases will require NVDA 2022.4 or
later and Windows 10 21H2 or later.
- The very
last releases of these add-ons will be a compatibility
update for NVDA 2023.1. Shortly after, these add-ons will be
marked as “legacy” in community add-ons website, and I will
give you at least 30 days notice before declaring them end
of life.
Cheers,
Joseph
|
|
|
Hi, Two more things: - For add-ons going out of support, I’m no longer accepting new issues/pull requests/feature suggestions/change requests i.e. features and code are frozen.
2. Add-on Updater: while not really marked as such, Add-on Updater will enter maintenance mode, starting with 23.02 release provided that progress is made to NV Access add-on store proposal. The last two features of Add-on Updater will be supporting and switching to the new add-on store infrastructure and deactivating the add-on altogether once NVDA comes with its own add-on updating/store mechanism. Cheers, Joseph
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io Sent: Tuesday, January 3, 2023 8:10 AM To: nvda-addons@nvda-addons.groups.io Subject: [nvda-addons] Three notices and a call: February releases, Windows 10 21H2 requirement, calling for maintainers to maintain most of my add-ons, one final time Hi all, Three important notices and a call: - Notice 1: version 23.02 of my add-ons will require NVDA 2022.4 or later.
- Notice 2: February releases of my add-ons (except Add-on Updater) will require Windows 10 21H2 or later (slightly relaxed from 22H2 requirement to support enterprises).
- Notice 3: apart from two or three add-ons, version 23.02 will be the second to last releases from me.
Some of you may remember a post from me last year calling on the community to maintain my add-ons I’m no longer maintaining (Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Resource Monitor, Sound Splitter, StationPlaylist). I did promise that if no-one shows up to maintain these add-ons, I will come back and update them in late 2022, which is exactly what I did for the last few days. But now I must ask you, one final time: please keep these add-ons going by finding new maintainers, and now, I’m adding Office Desk to the mix. I’m calling upon the community for maintainers one last time as I have no development plans for the listed add-ons after early 2023. The very last releases from me will be to make these add-ons compatible with NVDA 2023.1, and that can happen at any moment. Because I did say that February releases will require NVDA 2022.4, I am committing to that. In addition, as I noted a few days ago, future add-on releases will require newer Windows 10 releases or later, and that time has come: February add-on releases will indeed require Windows 10 Version 21H2 (November 2021 Update) or later. Originally I said 22H2, but to give enterprises time to migrate to newer Windows releases, I decided to support 21H2 in the time being. Besides, Windows 10 21H2 is the latest long-term servicing release for specialized devices. The reason for asking you to use newer Windows releases in February is to reduce uncertainty. As NVDA 2023.1 beta 1 can be released anytime, it wouldn’t make sense to dedicate an add-on release solely for Windows release requirements at this stage. Besides, this change reflects the fact that I really do not have any plans for the listed add-ons after February apart from compatibility update. One thing that’s going to be different from 2022: whereas I did say in 2022 that I will come back to update add-ons if no-one shows up to maintain them, I won’t do so in 2023 for an important reason: reducing NVDA community workload. If things go as planned, the only add-ons I will be maintaining after February 2023 will be Add-on Updater and Windows App Essentials; I wanted to keep Office Desk going and help coordinate its development, but looks like there aren’t that many people interested in developing this add-on. Even for Windows App Essentials, the future of this add-on is uncertain at the moment, as that’s the only add-on left in my lab once Add-on Updater is discontinued when NVDA itself starts checking for add-on updates. In summary: - February 2023 releases will be the second to last (true) releases of the following add-ons from me: Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Office Desk, Resource Monitor, Sound Splitter, StationPlaylist. These releases will require NVDA 2022.4 or later and Windows 10 21H2 or later.
- The very last releases of these add-ons will be a compatibility update for NVDA 2023.1. Shortly after, these add-ons will be marked as “legacy” in community add-ons website, and I will give you at least 30 days notice before declaring them end of life.
Cheers, Joseph
|
|
|
Hi all, Three important notices and a call: - Notice 1: version 23.02 of my add-ons will require NVDA 2022.4 or later.
- Notice 2: February releases of my add-ons (except Add-on Updater) will require Windows 10 21H2 or later (slightly relaxed from 22H2 requirement to support enterprises).
- Notice 3: apart from two or three add-ons, version 23.02 will be the second to last releases from me.
Some of you may remember a post from me last year calling on the community to maintain my add-ons I’m no longer maintaining (Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Resource Monitor, Sound Splitter, StationPlaylist). I did promise that if no-one shows up to maintain these add-ons, I will come back and update them in late 2022, which is exactly what I did for the last few days. But now I must ask you, one final time: please keep these add-ons going by finding new maintainers, and now, I’m adding Office Desk to the mix. I’m calling upon the community for maintainers one last time as I have no development plans for the listed add-ons after early 2023. The very last releases from me will be to make these add-ons compatible with NVDA 2023.1, and that can happen at any moment. Because I did say that February releases will require NVDA 2022.4, I am committing to that. In addition, as I noted a few days ago, future add-on releases will require newer Windows 10 releases or later, and that time has come: February add-on releases will indeed require Windows 10 Version 21H2 (November 2021 Update) or later. Originally I said 22H2, but to give enterprises time to migrate to newer Windows releases, I decided to support 21H2 in the time being. Besides, Windows 10 21H2 is the latest long-term servicing release for specialized devices. The reason for asking you to use newer Windows releases in February is to reduce uncertainty. As NVDA 2023.1 beta 1 can be released anytime, it wouldn’t make sense to dedicate an add-on release solely for Windows release requirements at this stage. Besides, this change reflects the fact that I really do not have any plans for the listed add-ons after February apart from compatibility update. One thing that’s going to be different from 2022: whereas I did say in 2022 that I will come back to update add-ons if no-one shows up to maintain them, I won’t do so in 2023 for an important reason: reducing NVDA community workload. If things go as planned, the only add-ons I will be maintaining after February 2023 will be Add-on Updater and Windows App Essentials; I wanted to keep Office Desk going and help coordinate its development, but looks like there aren’t that many people interested in developing this add-on. Even for Windows App Essentials, the future of this add-on is uncertain at the moment, as that’s the only add-on left in my lab once Add-on Updater is discontinued when NVDA itself starts checking for add-on updates. In summary: - February 2023 releases will be the second to last (true) releases of the following add-ons from me: Enhanced Touch Gestures, Event Tracker, GoldWave, Object Location Tones, ObjPad, Office Desk, Resource Monitor, Sound Splitter, StationPlaylist. These releases will require NVDA 2022.4 or later and Windows 10 21H2 or later.
- The very last releases of these add-ons will be a compatibility update for NVDA 2023.1. Shortly after, these add-ons will be marked as “legacy” in community add-ons website, and I will give you at least 30 days notice before declaring them end of life.
Cheers, Joseph
|
|
|
