-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add support for capistrano 3 #21
Comments
Please add support. |
Check my fork sauliusgrigaitis/capistrano-db-tasks@1c5f0ef for Capistrano 3 support. |
Can you do a pull-request? |
It's not backward compatible with Capistrano 2, merging back would make legacy users unhappy. |
What about moving those changed into a new branch with a new major version? Or you can change |
I believe best way would be to support both v2 and v3. Frankly, original code is very coupled, I don't see easy and nice way how to make support for v2 and v3. Maybe somebody has an ideas and time to make it. |
I think may be the best is to make a cap2.0 branch and to release this version (0.3?) |
legacy users should use rubygems.org and not github/master |
I agree with @sgruhier. Legacy users will use rubygems. If they will do |
Sounds like a plan. I can make pull request if no one has more ideas. |
you already made a PR no? |
Thanks for the support. |
It's my pleasure to contribute! |
Big thanks to @sauliusgrigaitis |
Capistrano 2 is now considered 'legacy' and is tagged as such on the capistrano repo.
The text was updated successfully, but these errors were encountered: