@Bibo-Joshi I understand there is a release plan, I have not abandoned this change, I can see tests are no longer passing due to merges that happen in the meantime.

If you guys decide to merge this PR, just ping me and I'll update the PR to be compatible and mergeable with most recent state of the repo.

@Bibo-Joshi I understand there is a release plan, I have not abandoned this change, I can see tests are no longer passing due to merges that happen in the meantime.

If you guys decide to merge this PR, just ping me and I'll update the PR to be compatible and mergeable with most recent state of the repo.

Glad to hear! We'll need to figure out what our plan for the next releases is, though, so it will probably take a while until we get back to this PR …

@Bibo-Joshi absolutely, that is understandable, in case if you guys decide to merge it to next release and I won't be responsive feel free to reach me in DM. Good luck!

TL;DR: Closing in favor of#1981

After internal discussion, we came to the conclusion that we don't want to continue implementing scheduling logic on our own and instead rely on a 3rd party library for that (see#1936,#1981).
One of the upsides is, that a cron logic is already included.
We appreciate the effort that was put in this PR and hope that you'll find the newJobQueue useful once it's finished :)

@Bibo-Joshi looking forward to try out the newJobQueue!