Is this repo still maintained?

[dodysw2]

Planning to adopt this for a large code base, but worried looking at the number of unresolved issues and last commit date.

[matt-harvey]

I was wondering the same thing. There are open PRs that would resolve some of those issues, but those too appear to be going unattended.

[steven-zou]

Same question

[phamdt]

perhaps the maintainers would like to vet a community supporter or two to help with merging PRs and reviewing issues?

[taylorchu]

Many people wonder why there is no update for a while, and here is why: we have been working on the v2 rewrite about a year ago. It fixes many issues (please see the readme), but most importantly, queue reliability. There were some incidents that were caused by gocraft v1, which moved jobs around in redis without atomic operation.

v2 runs smoothly for a year now in production, so I think it is ready for you to try.

[steven-zou]

@taylorchu @cypriss @hoffoo @snorecone

As we have built our own distributed job service based on this version, my question is, will this repo continue to accept some fix PRs?

[taylorchu]

yes. We are also looking for a maintainer for v1. If someone wants to be one, please comment here.

[rwojsznis]

v2 runs smoothly for a year now in production, so I think it is ready for you to try.

Oh my, why this gem is so deeply hidden? 🙈 maybe v2 is worth mentioning in the readme here for better visibility? 👏

[digininja]

Will the documentation for V1 still apply to V2? I'm fairly new to Go so the more documentation the better, obviously V1 has a lot, V2 doesn't seem to have any yet.

[hibiken]

If anyone is interested in trying out an alternative library, please check out Asynq.
It's currently under active development.

Any feedback would be greatly appreciated! Thank you!

[caldempsey]

I'd help maintain this!

[aanari]

Me too!