Suggestion: Issue Maintenance on Github

[chriscz]

Hi there,

I've noticed several issues are very old or seem to not be relevant anymore, it would be great if these can be closed because they create the impression that DelayedJob is buggy or unmaintained when this is clearly not the case.

The reason I bring this up is because I've been looking at the background job landscape of ruby recently for database-backed job runners and it looks like delayed_job is the only maintained one that works with MySQL.

[jpwynn]

create the impression that DelayedJob is buggy or unmaintained when this is clearly not the case.

@criscz since the last release was 2022-09-28, and the last closed issues was late 2023, are we still confident that's not the case?

I've been holding off migrating from Rails 5.2.8 to 6, then 7, while keeping an eye on the issues/releases, specifically because we rely so heavily on DJ and have been fervently hoping we do not have to replace it in our stack.

If you've moved off DJ, what did you find that worked for you?

[albus522]

There hasn't been a release because it hasn't been needed. DJ continues to work just fine for the vast majority of users.

The only actual issue that I am aware of is the job specific timeout interplay with the worker timeout, which is a weirdly complex issue to solve for.

[zspencer]

I've been holding off migrating from Rails 5.2.8 to 6, then 7, while keeping an eye on the issues/releases, specifically because we rely so heavily on DJ and have been fervently hoping we do not have to replace it in our stack.

We're running Rails 7 in production with Delayed Job without issue.