-
Notifications
You must be signed in to change notification settings - Fork 15
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
Test Sekken Swap for Savon v2 #6
Comments
Are sekken and savon v3 the same thing? |
Yep! Here's the thread for their reasons. Basically, v3 was a pretty major change and developing/testing on master was becoming really hard. Issues were getting mixed up and people were getting confused on which version to use so they thought it'd be better to stabilize v2 and then get a fresh start on v3. |
Sorry, to answer your second question- it is a bit unstable, but I'm interested in testing it out at some point! But, probably not anytime really soon. I've started working on both Savon and Sekken when I have time and I thought it'd be nice to try and use them both within real cases (like with the Marketo API) as they develop. I do use Markety in a production app for my day job so keeping this gem stable is pretty important! ;) |
Thanks, got a better understanding now. And yes, at least as an experiment, I think this would be a good idea, for the near future. |
Right now we're running Savon v2, but it might be advantageous to create a new branch with test for Sekken so we're staying up to date/can try and test different issues that might arise...
The text was updated successfully, but these errors were encountered: