I think that faUz has a good point, as I am worried as well about the number of issues that have been reported following the 3.2 release.
This also touches upon the topic “Which installation to use?” and field testing.
- Store Apps get automatically updated and if there’s issues with these, there’s nothing that the user can do about it.
- The same counts for the online version and the Chrome App version. Once a new version has been released, it will be coming, no matter what.
- Compared to this, the installed version has the advantage that one could wait a while until issues appear to have died out, or revert to a previous version (if one has been smart enough to keep a backup of the previous installer)
Some form of beta release schedule would sort out most the above conflicts.
- If someone wants to partake in testing the latest features, then allow them to install pre-release builds.
- Those who prefer stability over new functionality can opt to follow the stable releases.
Have Gravit considered a staged release schedule including beta/snapshot builds and more stable releases?
With an - I presume - vastly growing user base, this would be a wise move in order to prevent bad user experiences, bad press or users walking away.