Is there any reason why we shouldn't do this upgrade path:
1. Upgrade to 7.0
1.5. Deploy site to live <-- is this step needed?>-->
2. Upgrade to 7.1
3. Deploy site to live
From what I know, a jumpt straight to 7.5 involves more breaking changes, so that will have to wait.
We did like you have planned but without step 1.5.
I think though that you should consider going directly to 7.5, the job should not be so mutch more.
What breaking changes are you thinking of would be hard to solve?
OK, good to know.
I was thinking about the VPP migration, which in our case I assume would require a major clean-up.
I think you can do it without a cleanup or you can clean after migrate.
There is a lot of nice new functionality in the core soon to be released as well as upcoming add-ons that will require latest version to be able to use. Also, there has been quite a few performance improvements for the user interface in the packages released after 7.5 that you probably want to have, specifically if you have a lot of content. So I would definitively go for 7.5 directly.
The site we're upgrading relies heavily on scheduled jobs, and since the scheduler service is gone in 7.5 I'd have to do some work on that part as well.
Hoping to make the jump to 7.5 in very near future though.
The schedule is gone but you will not have to change a thing. The jobs works as they used to be.
OK - so I guess the only difference is that the jobs will not execute if the site is not pinged regularly. At least this is what we were told @ techforum in Oslo earlier.
Also make note that on some 7.x versions you will need to execute EPi upgrade scripts against database as well. Really hope you will eventually get hands on EPiServer vLatest :)
aaand... if your site heavily relies on scheduled jobs this tool may become handy. hahahha.... marketing spam :D
Thanks for the tip Valdis :-)