Release plan for Ultimate Cron 8.x-2.x

Can we just release another alpha, beta or a stable? The module is in use on a lot of site and I'd like to see it go stable. Let's identify what is blocking stability.

Maybe commit all RTBC patches, release a quick beta1 or rc then go with full stable a week or two later?

A new release would be wonderful! At this time Ultimate Cron is the only solution for Drupal 8 so probably it should deserve more attention...

In the meantime a new alpa3 release was on 9 February 2018 by Berdir. There were 2 commits, but there are still several active issues for Ultimate Cron, so would the goal of this issue be to identify those issues that are blockers for a beta release or are there any known D7 functionalities that the current D8 version doesn't offer as well, that are additional blocker other than the open issues?

Would be great to turn this into a plan for a stable 8.x release with security coverage

I'd like to bring a bit of attention to this issue again. The last non-dev release (alpha-4) is now 2 years old. Ultimate-Cron is powering lots of cronjobs on more than 50 of our D8 sites without any major problems. What is actually keeping us from going beta?

I support the call for a new release, preferably beta. I use ultimate_cron on almost all sites I build and would like to see some progress here.

I think #2842834: Remove unnecessary hooks is worth a wait and probably once the hooks are clean up, we should be able to get a stable release.

On my opinion #2692781: Make global setting ui dynamic and use it would be important to get in on beta/stable release since it introduces config/schema changes and would make clean-up easier and some other issues #2923922: Scheduler settings form is blank obsolete.

It would be really helpful if a new release(beta) will be done. Patches from RTBC are ready to commit and more from NR once.

Is there a time line for the beta and stable release? It would really help. What is needed to complete the steps?
And maybe a stable release for the basic functionality that is stable? I like this module, but can not always use it, because of the alpha state.

What help is needed to get a stable version out? A lot of organizations will not allow running any modules that are not stable.

Updated the issue summary for the issues that I found that should be finished before the beta/RC release. Maintainers might disagree with the list, but I'm sure they'd appreciate any help to complete any issue on issue tracker.

On general level the module has a lot of code inherited from Drupal 7 days. Also many issues would need someone to validate if the issue is still present and provide steps how to reproduce it.

A lot of cleanup was done in 8.x-2.x, a beta release will likely follow soon, please test now and report any issues.

+1 on getting this to a stable release. I use this all the time, but it would help immensely for it to get the security shield.

I have removed from the todo list an item that was marked outdated. I note all the must-have issues are done. Perhaps it is time for a full release and the other issues can be addressed in a patch release?

There are some commits past the last tag, so there should at least be another beta; there is an issue specific to that: #3544546: 8.x-2.0-beta2 Release Request

Thank you so much Sascha and Dieter for keeping Ultimate Cron going. 58,646 sites report using it.

We would love to ship it in Drupal CMS recipes. Recipes install with minimum-stability: stable, and 2.x is beta only, so the install stops with:

drupal/ultimate_cron ~2, found drupal/ultimate_cron[dev-2.x, 2.0.0-alpha1, ..., 2.x-dev (alias of dev-2.x)] but it does not match your minimum-stability.

A stable 2.x tag would open the door for everyone packaging recipes and products. Happy to help with testing, reviews, or anything needed to get there.