Upgrade path from CMS& R2

Vote:
 

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.

#89837
Aug 27, 2014 11:23
Vote:
 

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?

#89839
Aug 27, 2014 11:28
Vote:
 

OK, good to know.

I was thinking about the VPP migration, which in our case I assume would require a major clean-up.

#89840
Aug 27, 2014 11:51
Vote:
 

I think you can do it without a cleanup or you can clean after migrate.

#89841
Aug 27, 2014 11:55
Vote:
 

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.

#89842
Aug 27, 2014 12:07
Vote:
 

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.

#89843
Aug 27, 2014 12:17
Vote:
 

The schedule is gone but you will not have to change a thing. The jobs works as they used to be.

#89844
Aug 27, 2014 12:53
Vote:
 

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.

#89845
Aug 27, 2014 12:57
Vote:
 

Exactly.

#89846
Aug 27, 2014 12:58
Vote:
 

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 :)

#89871
Aug 27, 2014 22:17
Vote:
 

aaand... if your site heavily relies on scheduled jobs this tool may become handy. hahahha.... marketing spam :D

#89872
Aug 27, 2014 22:19
Vote:
 

Thanks for the tip Valdis :-)

#89887
Aug 28, 2014 9:21
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.