[GENERAL QUESTION] Status of this project?

[j0sh3rs]

Hey @hibiken -- Can you speak to the status of this project and whether it's still active/maintained? There are a lot of open PRs, many for dep bumps, and no activity on the project from you in 3 months.

Are you abandoning it? Or will we see an uptick in development in the near future? This project looks really promising for something I'm leading, but if it's not going to be active or maintained, I may need to rethink using it.

Thanks!

[kamikazechaser]

Hi @j0sh3rs. I am the other maintainer here. The project is actively maintained, just relatively slower with the release process. My wider scope is to support with

• Keeping the dependencies updated
• Latest Go compatibility
• Critical bug fixes
• CI/Docs

For the above I have discretion to directly push to master and create patch tags. For any other change, Ken would also need to approve it.

Right now we are preparing to release a huge set of changes with pending work described in #811.

[j0sh3rs]

Hi @kamikazechaser -- Thanks so much for your response and some detail into the project status. I'm excited to hear this is still under development, as the overall aim and features are wonderful. The native priority queuing, retry logic, and deduping are all fantastic features my team is excited to get for free by using this library, and it will save us a ton of time.

Appreciate you getting back to me on this so quick! Expect to hear more from me as we implement and thanks again for all the hard work on asynq!

[shchiv]

Hello @hibiken @kamikazechaser
Could you please provide an approximate estimation of when the v0.25.0 can be released?
or at least reusing Redis client can be merged?

[kamikazechaser]

@shchiv I have pinged @hibiken to review the PR's in v0.25.0 issue. Once I get his +1, you can expect it to progress.

I am also considering merging some of the changes into an unstable branch so that end users who know what they are doing can go get it.

[shchiv]

@kamikazechaser great thanks!