Sorry I don't get this approach? If 2.1 will come in a week what would you do then? Spend time to upgrade to master? Or go along in using master from start and if you bump into problems, create your patches and submit them to the framework so you can improve it?
I believe that's the problem with most of the people advocating for a fast release of 2.1. Nobody is looking at the opened issues/PRs to see if something they are going to use is even flagged by a PR/issue so that they can take the decision to use master or not. Also, whenever someone using the framework bumps into a problem at least an issue should be risen into GitHub so that other people contributing are aware of it/fix it if you don't have time to fix it, which I doubt since you need to further with the project, right? Best regards, Florin On Tuesday, May 1, 2012 12:46:55 AM UTC+3, Julien DIDIER wrote: > > Symfony2.0 has been released since less than a year. > I'm developing a new SOA appliance for my customer. > > For some business logics, we are fetching 2.0.x. > But we have some limitations from the 2.0, that could be fixed by the 2.1. > > It's like a trap, for developers, and for contributors. > I think, developers could need this version quickly as possible for more > beautiful lines of code. > -- 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
