Hi! I know very well. As you might recall, i had some patches that i have sent to you in the past. I know that 'this thing, done like this works in my case' is not a framework way.. however, in the case of some patches is easy to test if the issue is there, and, if the patch works. However, we must think as well what other implications would have this patch. But, there are some patches for english documentation that would be easyer to implement, as most of us are able to read english. The tickets that are not understood by us, we forward them to symfony-docs teams. Anyway, i think that before "fixing" bugs, we should see if they are reproduceable.. if not, then, they should be moved in a new milsestone, and remain there till someone is able to reproduce them. I know...this migut take a while... but ....
sent via htc magic On Jan 28, 2010 7:24 PM, "Fabian Lange" <[email protected]> wrote: Hi Alecs, yes there are many tickets with patches. But let me assure you that valid easy patches have been applied within days. Those left over are debatable, possible invalid, bad design or just not working patches. Documentation patches tend to be inclomplete, as you should check other languages and other versions (currently 3 symfony versions * 2 orms * 1-10 languages = plenty of docs) There are many tickets which say: oh just add this here and then MY case works. But thats not how we can develop a framework. I think you will understand when you take a deeper look at the patches. Fabian On Thu, Jan 28, 2010 at 9:54 AM, Alexandru-Emil Lupu <[email protected]> wrote: > Ok. > Sorry fo... -- You received this message because you are subscribed to the Google Groups "symfony developers" group... -- 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.
