Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecation warning in Rails 5 #143
Given this issue and the last commit dating back to May 2017, I have to ask the question: Are you still maintaining these gems? It's totally okay if you have lost interest, happens to all of us sometimes, but I (and others I presume) have to decide where to go from here and whether to stick to "timeliness" and friends.
Also, there are 129 forks. If you ask the community, someone might step forward and continue your work by adopting the "timeliness" gems.
In any case, thanks a bunch for your work on these gems!
Hi all. I haven't given up, I just haven't gotten around to upgrading my own apps to Rails 5 which has always been to the trigger. It all comes down to my availability which is has been terribly low I'm afraid.
So my Rails 5 upgrade plans are within the 2 months. I have been reluctant to hand off this project off because I am still actively using and interested in maintaining and I really wanted to clean it up a lot and shed the cruft from supporting old AR versions.
Appreciate the interest and the frustration.
Also currently there are no compelling PRs to do the upgrade. So it has not been a simple choice of merging a PR from the community which would accelerate all this. So if someone is interested in pulling together a PR of changes with specs we can review and discuss that would be excellent.
@adzap I have faced this now as an exception as I am working on Rails 5.2.0.