The upgrade to 1.4 is a simple package upgrade. Before you make the leap to 2.0, I would recommend upgrading to 1.6 first. This should be a drop in replacement and you can continue on 1.6 as long as you’d like. There are a number of deprecations in 1.6 to help you prepare for the 2.0 upgrade. Some of those deprecations do not have replacements in 1.6 due to various reasons but many do. Once you eliminate the deprecations you can, upgrading to 2.0 should be seamless as well. Once on 2.0, you can eliminate the remainder of those deprecations by migrating to the new APIs at your own pace. The 2.0 update is worth it (yes, I’m biased) as the API is leaner and more consistent. The formal migration guide hasn’t yet made it in to the docs but i’m working on that now. There’s a skeleton guide in the github repository, however.
If you run in to upgrade issues, please file an issue at on github and I’ll do my best to get you sorted.