+1 for releasing now maybe by the time when the Form changes are finished/stabilized there will be another component which also has a super cool new feature which should go into the release. (And it also evntually breaks BC). Then we are in the same situation as now. So should we wait 4 months now for the Form Component, then another 4 months for Component x, and so on?
Also Symfony already has some BC breaks. And even after the next release there will surely be more BC breaks. The more breaks there are the harder it will get to upgrade. To fix a few code/config parts is OK. But as it gets more it becomes a frustrating work which is not good for Symfony and also maybe prevent users from upgrading. On the other side if we are releasing now the user can choose for himself if he wants to upgrade now and get all the new features and fix BC breaks step by step or if he wants to wait longer and do all the hard work for fixing all the BC breaks at once. Also if we release now (and in shorter cycles in general) for the end user the project seems more active. For the end user the releases are what counts and not the commits to the repository. -- 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
