Hi guys! I would like to wait.
There are 2 things that make an upgrade a headache: 1) BC breaks 2) Lack of documentation, examples, not-yet-updated 3rd-party bundles, and unpolished states for new features. I think that the world (via docs, blog posts, bundles, those bundle's READMEs) is still largely catching up with 2.1. The RC stage will help with this, but I think that #2 will be less of a big deal if we wait. Composer is one big area of concern for me. If we release 2.1 in the next few weeks, there may not be any BC breaks, but Composer will represent a major change and challenge. I work with several individuals who have already upgraded to Composer, and it's been a painful process for each. Composer is great, but I'd like to give some more time for everyone to catch up on it. Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://knpuniversity.com Twitter: @weaverryan On Sun, Apr 29, 2012 at 4:46 AM, keymaster <[email protected]> wrote: > > I think the answer depends on two things: > > 1. If it is easy to upgrade from 2.0 to 2.1 after reverting the BC > breaking form stuff - then yah, it's a no brainer, release 2.1 now and > everyone gets the goodness. What's the question? > > 2. On the other hand, if it is already difficult to upgrade from 2.0 to > 2.1, I'd say only put people through the pain once, in July/Aug (with - and > this is THE most important thing - very detailed and clear documentation on > how to do the upgrade, and maybe even some automated tools to help, where > possible :-)) > > Your call, Fabien. :-) > > > > -- > 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 > -- 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
