Short Story of a Long Migration (from Java 7 to Java 8)
jobs.zalando.com
jobs.zalando.com
Not sure this is a better strategy - it accumulates technical debt.
I think you should try to update as much as possible and stay ahead of the curve. That way you can reap the benefits of performance improvements, bug fixes and richer APIs. Sure, it makes sense to not use the bleeding edge, but being on the oldest possible version doesn't seem to be a good strategy either.