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
