@Ralf: well, there's "composer.lock" for that. You don't run the upgrade on the production server (that is dangerous exactly like upgrading a linux distro without verifying that things won't break!), you just run an "install" with the updated "composer.lock" once it has been updated (and tested) in your dev environment. That updates dependencies to the state defined in "composer.lock", which is quite amazing in terms of spared time.
Marco Pivetta http://twitter.com/Ocramius http://marco-pivetta.com On 5 August 2012 17:10, Ralf Eggert <r.egg...@travello.de> wrote: > Hi Dennis and Marco, > > thanks for your comments. I never thought about the upgrading part. > Though I will always first upgrade on the development server and later > on on the production server. Upgrading on the production server with the > composer seems interesting, but I am not sure if I really want that. > > Best regards, > > Ralf > > -- > List: fw-general@lists.zend.com > Info: http://framework.zend.com/archives > Unsubscribe: fw-general-unsubscr...@lists.zend.com > > >
