Influence the future of symfony
Last month, I shared my vision for symfony 1.3. To involve the community in the process of deciding what to do for symfony 1.3, I have opened a user voice page where everybody can suggest enhancements for the 1.3 version of the framework.
For now, the most requested enhancement is to work on performance. Enhancing
performance is not an easy task. The framework is already quite optimized and
making it faster will certainly mean removing things, doing things
differently, removing some compatibility layers, and perhaps break
compatibility altogether. The symfony core team will suggest some enhancements
in the coming weeks, explaining the pros and the cons. The community will then
have the opportunity to vote on them and you will have the last word (be ready
to add some
-- strings as comments as you did for the Jobeet design
The third and fourth most voted suggestions are contradictory: make Doctrine the default ORM and do not make Doctrine the default ORM. After some thought, I think I have found a solution to make everybody happy. There won't be a default ORM in symfony 1.3. Whenever you will create a project, you will have to choose between Propel, Doctrine, or no ORM at all.
If you want to vote for an existing suggestion, or add a new one, you still have one week left as the "Feature brainstorming" phase ends at the end of the month.
Influence the future of symfony symfony.com/index.php/blog/influence-the-future-of-symfonyTweet this
Become a certified developer! Exams are online and available in all countries.Register Now
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.