I will do whatever I can to better symfony and help fix bugs, but really, what is the rush? It's something I've been thinking about ever since this release schedule was announced - why give yourself a hard date over such a tremendous change in the codebase? And what about the core plugins? It seems to me that there are several improvements for sfGuardPlugin that have been pushed back for months already. A quick look at the track revealed more than 30 tickets with status "ready for core team" and 16 for sf 1.3, one of which (#7537 that I reported a while back) shows that sfYaml can't be trusted with an arbitrary array of data.
Isn't the smarter option to postpone the release for a week and be sure that when you're releasing the new major version of symfony it is in the best possible form? On Nov 27, 1:41 pm, Fabian Lange <[email protected]> wrote: > Hi, > I partially agree with you. Yes there are some bugs in, and yes the > impression might come up that the release is still super buggy. > But in fact I think that is not true. > The quality is not worse than the previous releases. In fact I think > the quality is better, the performance is better, and it contains > major upgrades for propel and doctrine which are (as you said) much > better. > > From my impression the majority of the last minute bugs are imperfect > upgrades, which can be solved either by symfony or just by adopting to > a changed behavior. > There is still some time. Test, Test and ticket everything whats > wrong, we will fix it over the weekend :) > > Fabian -- 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.
