I understand needs for rapid development, especially in last weeks around Logitech, but I would like to know what is changing in next iversion installed by me. Currently I have 6.0017 but I’m lost - what was changed, what new features were added of bugs were fixed. I don’t see the information in application (during installation and later in Release Notes & Documentation).
I see big potential in many areas but don’t know what is new, what can be done etc. The documentation is rather not updated in last months.
Could someone show me where to track changes and new features?
For a one-person project where the developer is able to release several alpha versions every day, I really wouldn’t expect detailed release notes for test builds. Especially when in most cases it’s just bug fixes anyway.
Andreas usually describes all the changes properly with the final releases. I’d rather he focuses on development than on writing up fixes. 
1 Like
documentation is updated almost daily (mostly small additions) 
But yes, the forum here is the only place where references for most little fixes and improvements are posted, most of the time in direct response to a user request. The release notes are then updated once the stable release is being pushed
May I propose add tags in this forum n format like this #version-x.y.z when you write - “It will be fixed in next version” - it gives the chance to search forum for selected fixes/changes.
You misunderstood my question - I don’t require to update docs for each alpha version - as person writing software for 35 years I fully understand the process. But if I see in forum - “it will be fixed in next (alpha) version” - I always wonder is it the version yesterday updated by me or maybe it will be that available tomorrow.
tags are a good idea, I might try this!
1 Like
