I don't mind the BC breaks as long as they are well documented, my only concern is that we keep releases coming. Changes in 2.1 are great, and needed (imo) with or with out the new form logic. Personally as much as I want the new form stuff, I want other code more. In addition it is just a release. Yes it implies maturity (which 2.x will gain either way).
I am for releasing 2.1 asap. Planning on a three month window gives time for form to get wrapped up, tested and completed. Delaying will does not really help us aside from a revision number. And what happens is for some reason form is not 100% ready in 3 months, do we wait more? (I don't want to sound like I don't think Form will be complete, but things happen in life and not all things can be foreseen). As for trying to not break BC multiple times, it is an admirable goal. But not always required. I expect some upgrade issues on major revisions. I don't like the upgrade issues, but it happens. On Apr 30, 2012, at 11:49 AM, Bernhard Schussek wrot > 2012/4/30 Thomas Lundquist <[email protected]>: >> 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. > > Many people here comment about the BC breaks in the Form component as > if they needed to rewrite their complete application with 2.1. This > will not be the case. > > To put this into perspective, you have to divide the BC breaks into > three categories: > > 1. Breaks that affect a majority of users and will be hard to fix > 2. Breaks that affect a majority of users and will be easy to fix > 3. Breaks that affect a minority of users > > Breaks in category 1 should worry you. But most - if not all - breaks > in the Form component belong to either 2 or 3. So, this should really > not be the end of the world, no matter if we release 2.1 now or later. > > Bernhard > > -- > 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
