We're facing a problem that affect the user experience: the gap between release builds.
There's no need to wait for long to a new update affecting user experience because if the release build has some unexpected behaviour users must wait until the next build to get it fixed. Each release takes its time to being released for certain reasons and I personally think this should be solved by improving the way updates are deployed to users.
I consider the best solution is to make a "triggerable workflow" which will allow us to automatically build releases when needed with the latest changes from the repository without having to wait until "most things gets fixed to make a release". This would considerably decrease the gap between updates and improve the user experience. As an addition from the client-side I can improve the way updates are installed by getting the user directly to the installer once the build is downloaded.
We're facing a problem that affect the user experience: the gap between release builds. There's no need to wait for long to a new update affecting user experience because if the release build has some unexpected behaviour users must wait until the next build to get it fixed. Each release takes its time to being released for certain reasons and I personally think this should be solved by improving the way updates are deployed to users. I consider the best solution is to make a "triggerable workflow" which will allow us to automatically build releases when needed with the latest changes from the repository without having to wait until "most things gets fixed to make a release". This would considerably decrease the gap between updates and improve the user experience. As an addition from the client-side I can improve the way updates are installed by getting the user directly to the installer once the build is downloaded.