Just a note, Doctrine requires 5.2.3. At first, it was thought 5.2.2 was not affected by the segfaults, but I have done some tests and 5.2.3 is the only version where I did not experience any crashes. - Jon
On 7/16/07, Matthias N. <[EMAIL PROTECTED]> wrote: > > > On 16 Jul., 18:49, Fabien POTENCIER <[EMAIL PROTECTED] > project.com> wrote: > > As with any Open-Source software, there is no definitive deadline for > > symfony 1.1 but I will try hard to have a first beta by the end of > August. > > > > I think we need to bundle a default ORM with symfony. I don't want to > > force user to install a plugin as a first step to begin for every new > > project. I also want to have only 1 "preferred" ORM for symfony. It's > > much easier to update documentation, tutorials, ... > > > > The way Propel is bundled in symfony since 1.0 is pretty much a plugin > > (thanks to chtito work). All files are in a single addon/propel > > directory (+ Propel itself in vendor/propel). > > Ok.. you are the boss. :-) > But it would be great if you could add a task to completely remove > Propel or a switch for freeze to not freeze Propel. This would help > people using Doctrine. > I run into proplems trying to remove Propel some time ago.. but > unfortunately I can't remember why.. > > > > As far as form/validation is concerned, we need to make some more > > changes in the core before it can happen. The view and sfExecutionFilter > > refactoring, ... are first steps to be able to implement the new > > form/validation system. Next step will be to convert helpers to > > classes/objects. > > > > As a side note, I'm always looking for people willing to help. > > > > Everybody can help in a lot of different areas: answering questions on > > the ML and the forum, writing documentation, writing plugins, ... > > > > But we also need more people willing to help for small things. For > > example, there is a lot of opened tickets that need some attention. A > > lot of them are very simple tickets. If someone can create a patch, > > write some tests and update the documentation, it will speed up > > inclusion in the framework greatly. > > The problem I see is to keep track about who is doing what. I could > work on some stuff but I would like to see / mark somewhere who is > working on what so I don't work on something another is already > working on. > > For example I'm about to refactor the things around action stack / > controller / filter chain. > > Regards, > Matthias > > > > > > -- Jonathan Wage http://www.jwage.com http://www.centresource.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 -~----------~----~----~----~------~----~------~--~---
