Hmmm I am no dev, however when I do testing and some admin stuff,
wouldn't you have folders set on the serverside, dev versions went in
one folder, stable versions went in another.
Either that, or have some string in the manafest that would tell the
server if it was stable or not, then it would be automatically assigned
to the right place.
Either way, it would be good if devs had an easy time of uploading to.
You would only have to contact the admins if stuff never came out.
In addition you could have set a time of the night or something where
everything was pushed out to each channel automatically.
The dev could force push things as they are now if they wish but even so.
On 27/03/2017 4:42 p.m., Dennis Long wrote:
This would certainly be easier for the user and should be added asap.----------------------------------------------------------------
Thanks.
From: nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph Lee
Sent: Sunday, March 26, 2017 11:40 PM
To: nvda-addons@xxxxxxxxxxxxx
Subject: [nvda-addons] Add-on template: proposed changes to support add-on
updates and channel selection
Fellow add-ons community members,
As some of you may know, I'm working on ability for NVDA to check for and
download add-on updates. This project consists of a client UI and update
experience, add-on update info retriever and protocols, and a server-side
implementation to gather add-on versions and other metadata under one roof.
More info about this project can be found at:
https://github.com/nvaccess/nvda/issues/3208
At the moment the client UI is done. Once NV Access comes up with a protocol
and server-side facility, I'll update my client UI bits to point to new
capabilities. But this is just the start, as bulk of this project relies on
cooperation with add-on writers when it comes to making our add-ons support
updates. In order to do so, I propose the following changes to the add-on
template and manifests:
* Update channel: I propose adding a new manifest key named
"updateChannel" that'll let NVDA know which update channel should be
consulted when checking for an add-on update. By default, this key will hold
a null string (None), or for add-ons that does not support updates, this key
will not be defined. For most add-ons, possible channels could be "stable"
and "dev". The add-on author must notify server-side admins or reviewers
whenever channels need to be added, changed or removed.
Comments are appreciated.
Cheers,
Joseph
