Propel 2 : What could it be, and do you want to be part of it?
It's been only a year since the Propel project changed hands. In the meantime, the 1.x branch saw two major releases (1.4 and 1.5), and keeps evolving at a good pace.
3 comments
The idea behind a new Propel is to rewrite the internals of Propel, while keeping the API (as much as possible) backwards compatible with Propel 1.x, to keep the upgrade process simple.
So why should there come a new version of Propel, when the external API will remain (mostly) the same? First of all there currently are some limitations and security issues that cannot be solved without breaking backwards compatibility. New functionality has already been written so you can avoid these risks, but it would be better to prevent the risks completely!
Besides that it would be nice to make use of the efforts that are punt in Doctrine2. Not only to combine forces and improve the overal quality and functionality of the ORM business in PHP, but it would also make it easier for (Symfony) plugin-writers to create one plugin that can be used by "both" ORMs.
Read more in the post Francois just published while I was writing this ;) http://propel.posterous.com/propel2-will-be-an-activerecord-implementatio
Looking forward to a great new project!
