Upgrading SilverStripe 2.x to 3.x

Can anyone give an indication if there will be a supported upgrade path for users with site on 2.x wanting to upgrade to 3.x
e.g. list of pre-reqs, upgrade scripts etc. module compatibility etc. etc....

I'd appreciate some information on this if there is anything on the radar expected in the not too distant future.

Assuming we have reached a bona fide release candidate for 3.x later in the year, would there be an approved migration method published or are site owners going to have to go through the process of trawling changelogs to ensure they get 3.x to a fully working state post upgrade.
It would also be nice to have someone put together a module compatibility matrix for the most widely used standard modules available to download.

I think you might want to review the developer gogle group where most of the discussion is. For eaxmple one of the main projects for the GSOC is the module directory and how that can be handled in the future. Currently there is nothing that will address the module situation.

I'm suprised that the link didn't cover the upgrade stuff as it covers each upgrade within 2.x fairly well and then in the case of a 2.4.x to 3.0.0.beta it is so comprhensive I was really impressed. Ingo has mentioned several times that upgrading is going to be painless in the form of using modules to fill in depreciated/removed functinoality (even the CTF!) but it is still early days - I don't expect to address any of this fro about 6 months - probably 3.1.x - after it is extermely stable.

No. I can modify the odd bit of PHP and can slowly muddle my way through many things, but my understanding of what is being talked about in the upgrade procedure linked above coupled with the extensive branches off to other areas makes it so that I will NEVER be able to upgrade that way.

It is more likely that I'll try to begin again from a fresh installation and try to manually copy/paste my blog entries across. A bit of a PITA, but it's the only way I can see to migrate forward.

The point is I that I use SS as a communications tool and I am no longer wearing a developer hat (and when I did it was for a totally different coding language). I'd like to be able to run a script which migrates from version to another and not be messing with replacing statements, variables and function calls. I suspect I am not the only SS user with this point of view.