Hi Joseph,
I would prefer the current version scheme itself, and perhaps other
users may even get confused rather than crystallised by this version
scheme change. If only the add-ons that you maintain would adopt this
new version scheme, although it would streamline with NVDA core it
would deviate from uniforming with other community add-ons. Also, if
majority of developers were to deploy this approach then users may
even be left wondering why some of their add-ons are perhaps of 2015
or older. :)
The number ascent system for add-on versions seems sufficiently
functional, as it permits scope for delays in release of new versions,
is short and re-callable even if we use decimals to indicate minor
updates.
An add-on updater for all NVDA community add-ons would really be
appreciated, and despite the magnitude of the undertaking, I perceive
that this may not only impact and benefit users, but also give a
cogent reason to third party unofficial NVDA add-on writers to submit
their works to the community portal, perhaps.
Thanks.
On 7/29/16, Roger Stewart <paganus2@xxxxxxxxx> wrote:
I like this. It also follows the nvda way of giving year and version
within that year.
Thanks.
Roger
On 7/28/2016 10:43 AM, Joseph Lee wrote:
Hi everyone,
For the past few years, I used major.minor versioning scheme for my
add-ons except Windows 10 App Essentials. The major number was
incremented whenever a version with new features was released, with
minor version denoting minor enhancements, fixes and translation
updates. Although it worked out well, it led to an issue where people
found out they were using old releases (also caused by lack of add-on
update facility).
To make it easier for people to find out which add-on version they are
using, to make add-on versions uniform across add-ons and to make new
features available in a predictable manner (via time-based releases),
I’m thinking about migrating add-on versioning scheme for my add-ons
to follow year.month designations (for example, GoldWave 16.08). This
would allow users to easily find out which version of the add-on they
are using so they can compare against latest version out there, and
for me to release new versions upon request and on a timely manner. It
also helps in eliminating major.x maintenance branches so maintenance
can be performed from master/stable branches (an exception is for
add-ons that have long-term support (LTS) branches such as SPL Studio).
Comments from users of the following add-ons are requested:
·Control Usage Assistant
·Easy Table Navigator
·Enhanced Touch Gestures
·GoldWave
·Resource Monitor
·StationPlaylist Studio
·Windows 10 App Essentials
Comments from others in the community are also welcome. Thanks.
Cheers,
Joseph
