How to survive the stabilization phase

Date: 2013-05-10

As you might have noticed, we reached a phase in the stabilization process where we clean up things and try avoid future architecture problems. This leads to lots of BC breaks (and we don't want to clutter the codebase with legacy support before a version 1.0 is even out).

We now created a set of alpha tags for all relevant bundles. If you want to stay at the edge and don't mind adjusting to the occasional BC break, please keep using 1.0.* and report any issues. Otherwise, you can pin to the following versions to keep status quo and update the tags manually when you want a new feature.

    "jackalope/jackalope-jackrabbit": "1.0.0-beta1",
    or
    "jackalope/jackalope-doctrine-dbal": "1.0.0-alpha1",

    "doctrine/phpcr-odm": "1.0.0-alpha1",
    "doctrine/phpcr-bundle": "1.0.0-alpha3",
    "sonata-project/doctrine-phpcr-admin-bundle": "1.0.0-alpha2",
    "symfony-cmf/core-bundle": "1.0.0-alpha1",
    "symfony-cmf/block-bundle": "1.0.0-alpha3",
    "symfony-cmf/content-bundle": "1.0.0-alpha2",
    "symfony-cmf/create-bundle": "1.0.0-alpha1",
    "symfony-cmf/menu-bundle": "1.0.0-alpha2",
    "symfony-cmf/simple-cms-bundle": "1.0.0-alpha2",
    "symfony-cmf/search-bundle": "1.0.0-alpha1",
    "symfony-cmf/tree-browser-bundle": "1.0.0-alpha2",
    "symfony-cmf/routing-bundle": "1.1.0-alpha1",
    "symfony-cmf/blog-bundle": "1.0.0-alpha1",
    "symfony-cmf/routing-auto-bundle": "1.0.0-alpha1"

You can alternatively depend on symfony-cmf/symfony-cmf which includes most of the above bundles. This will all get better once we have stable releases. Then we will not do BC breaks without updating the minor version, so that you can safely depend on 1.0.*.

Note that the RoutingExtraBundle was renamed to RoutingBundle. There is 1.0.1 of RoutingExtraBundle which will be the last version with the old name. The above tagged versions already use the new RoutingBundle name. RoutingBundle master branch is already called 1.1 now. It dropped Symfony 2.1 support.

prev next