I’m not a programmer, but it seems to me that some of the bugs associated with KOS 1.6.0 were so glaring and obvious (I’m looking at you, call notification bubble!) on day one that there must be a lack of end-user real-life beta testers. Is there a way to get involved with break-testing release candidates a few weeks before rollout like a lot of apps and linux distributions do?
Thanks for all you do, developers! I love my Kompakt and know the OS is developed and maintained by a small group and not, say, Google. You do great work. Keep it up!
That is completely fair, and I think it is a valid model for a smaller development team to roll out a release and just be ready for feedback and then follow it up with a quick update, especially with what I assume to be something of a niche user base.
Urszula: Be sure to also pass on the latter part of the post - “Thanks for all you do, developers! I love my Kompakt and know the OS is developed and maintained by a small group and not, say, Google. You do great work. Keep it up!”
It can be really disheartening when you only get feedback when something doesn’t work. I think a lot of the community shares the attitude that whenever something doesn’t work as intended, we want to know if there is anything we can do to help.