I would dearly like to use this app but many things turn me off and the upgrade path is one of them. ALL competitors offer simply inline/inplace upgrades from their admin consoles but simply selecting "Upgrade".
Why do the developers of silverstripe wish to do things so different??
Surely there must be an easier way to upgrade.
Oh and whilst i am having a winge, Where is the real blank site start from scratch guide or step-by-step offline documentation?
An theme...well lets not go there..
Sorry but there has to be easier ways of doing things?
if someone wishes to show me how then please step foreward.
You have a very good point of the upgrade path. I think to understand why its one thing thats not there that seems obvious is that the usual SilverStripe installation (well at least historically) has been on the concept of web developers developing the site and handing it over to more non techy / enterprise level users. If we had an upgrade function in the CMS could you imagine the amount of broken live sites when a user clicks update and they have no idea of whats happened!.
This is one area that is going to be a feature of a future version. Were looking at introducing a module management API (including the backend management) and integrating more tools for the CMS (see http://open.silverstripe.org/ticket/2865 and http://open.silverstripe.org/ticket/3652)
How I deal with upgrading is that all my sites run on git or svn so all I need to change is the location which I pull from and I get the new changes. However its quite hard to make sure modules are compatible so again with the module management API managing dependances might be alot easier in the future!