On Mon, Apr 30, 2012 at 07:36:21AM -0700, Florin Patan wrote: > > I'm currently running master against a production env with a couple of > countries, a couple of million of users (and I'm not allowed to say more) > but the upgrade from 2.0.7 (if I recall it correctly) to master was pretty > painless, only 3 days or so to migrate the code, run the automated tests, > check for the performance gains/drops and so on and it feels pretty good > when I can do an upgrade with little to no effort all by myself, so that > the rest of the team can focus on development. I'd say master is very > stable for us so far, using it since 1st of February
Good to hear and it makes me want to start using master with the project I am about to start now. I'll prolly end up with that if we choose to go for Symfony2. The other Sf2 projects I have running already is of course 2.0 and I have a slight feeling I shouldn't spend too much time on forms if I dont want to be stuck there. > And to be back on topic... Master already has some large changes so we > should rather finish the changes for Form, make it stable then push 2.1 and > then start doing smaller release cycles with less BC breaks as the current > upgrade. Seems like this option is the one with the most votes. Thomas. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
