when will project get diverse into beta and stable versions?

[kayyum-j6ho1ms5]

the analogy to replicate what, how, why, when - evolution will work. i mean beta version for faster feature implement and get feedback from community if it increase app use-case or performance then it will be merge into stable branch otherwise get eliminated.

i ask for favor what Fedora Red Hat Inc. do for increase feature usability. Red Hat -> stable version, Fedora -> beta version. all new feature implemented and tested in Fedora then if it found useful, then it merge into Red Hat!

that's way our Clock reach a stability where no app can withstand or comparable.

[BlackyHawky]

@kayyum-j6ho1ms5
Hi,

I completely understand your request but these projects are not comparable in terms of either the number of users or the number of maintainers...

Until proven otherwise, there are no major bugs as there were when version 2.10 was released, so we can consider the published versions to be stable.

However, maybe that I could release beta versions more often so that users can benefit from the latest commits more quickly...
But knowing that I publish a release version once a month, is it really necessary and/or useful?

(By the way, the next version will be released next week.)

[kayyum-j6ho1ms5]

is it really necessary and/or useful?

yes, a lot. with stable version (release once a month or once in three month) made a lot of difference for user who heavily depend on app.

why, when new version released we supposed it work like yesterday + new feature, but when timer or alarm not trigger when it supposed to do it make situation worse; i never know until it break for unknown reason.

here the story why it make me to discuss about versions
few day ago, i update the app to new version; timer was supposed to wake me up at night after 4hour then i sleep (after setup timer). the timer execute and expired but with no sound and vibration. i was spelt for 9 hour that day; mine entire day schedule, work, monitoring get messed up and it happening again and again until i 'clear app data'. i revert to previous version ASAP till now not a single incident happen.

this is the biggest reason i'm afraid, till now i'm still using version 2.23 in personal phone and latest version on secondary device

[kayyum-j6ho1ms5]

my major concern is if it can happen with me, then it can be happen with others too

[BlackyHawky]

There's something surprising about everything you're telling me...

Why didn't you open an issue? Especially since it's possible to provide the app logs...

We're not the only two using the app, and as far as I can remember, no one else has reported any issues related to what you're saying.

And if, instead of opening an issue to report it, you revert to a previous version, how do you expect me to improve the app properly?

It's still strange to tell me that here, in a discussion...

In addition, before releasing a new version, I pay close attention to the alarms because it is obviously my alarm clock app.
And I'm even more careful when I have to modify the app's SQL database.

The test I perform is quite simple: I set 2-3 alarms and install the next version to be released. I play around with the settings, and if the alarms go off, everything is OK.

The most important question for me remains: why do people uninstall the app instead of reporting it to me? 🤔