-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of the project #47
Comments
This was referenced Jan 25, 2018
glongman
added a commit
to Fullscript/resque-cleaner
that referenced
this issue
Dec 27, 2019
resque-cleaner is a dead project see here: ono#47
This was referenced Dec 27, 2019
glongman
added a commit
to Fullscript/resque-cleaner
that referenced
this issue
Dec 27, 2019
resque-cleaner is a dead project see here: ono#47
glongman
added a commit
to Fullscript/resque-cleaner
that referenced
this issue
Dec 27, 2019
resque-cleaner is a dead project see here: ono#47
I just forked and pushed https://rubygems.org/gems/resque-cleanerer 0.5.0 including some PRs on this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I notice that there are still many people using this library. I am very thankful to everyone and feel some responsibility to explain the status of the project.
I no longer use this library by myself. In fact, I haven't used Resque for long time. For day to day job, I mainly use Elixir. I have to admit that I'm quite behind the scene.
I would say that this library is maintenance status and here are some notes to clarify.
You might ask for transferring the ownership but I am reluctant to do that in following reasons.
I hope you don't have a huge objection to the decision as Resque itself is not much active for years.
Thank you so much for your interest on this project.
And thank you especially to all people who have contributed! 🏅
The text was updated successfully, but these errors were encountered: