No coupling of release cycles anymore;
Move code to the organization that actually maintains it;
Avoid Symfony suggesting Doctrine is the only way for persistence; Symfony wants to focus on providing the View and the Controller abstraction and not make suggestions about the Model.
The Symfony standard edition has been updated to reflect this change.
In your code, you will have to change references to the Doctrine classes; for
Registry class must be changed from
DoctrineMongoDBBundle are now maintained in the Doctrine organization as
well; however forks have been created in the Symfony repository to make all
the 2.0 apps out there backwards compatible (you just need to be check that
your are using the 2.0 branch).
The new repositories are here:
You can find additional information about the move on the Doctrine blog.