Support Capistrano 3
Or is this not done for some specific reason?
No specific reason, just haven't converted my stuff to cap 3 yet. Do you know what it would take to make this support cap 3? Are any of the things done by this built-in to cap 3 now?
You are welcome to fork this into a cap 3 version, and/or pull request.
Im afraid I dont know capistrano deep enough to make a good estimate here. I do not believe any of the functionality is internal to cap 3 though.
Has this ever been thought about again? lol
I am not using this myself or or supporting it anymore, sorry! You are welcome to fork it though!
If someone forks it and wants to do a release under the same name, I would consider giving you rubygems release privs.