Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

Commit

Permalink
Merge pull request #15 from symfony-cmf/news-towards-release
Browse files Browse the repository at this point in the history
add news entry moving towards release 1.0
  • Loading branch information
dbu committed Feb 26, 2013
2 parents 9fdaf4b + f54d851 commit a980d2b
Showing 1 changed file with 14 additions and 2 deletions.
16 changes: 14 additions & 2 deletions src/Cmf/MainBundle/Resources/data/page.yml
Expand Up @@ -217,6 +217,18 @@ static:
in terms of language, details and introducing each concept in the right order. This is the kind of thing
that is really hard for the original authors to get right, since they tend to be oblivious to such aspects.
towards-version-1.0:
name: "towards-version-1.0"
parent: "/news"
title: "Towards version 1.0"
label: false
template: CmfMainBundle:Cms:news_detail.html.twig
publish_start_date: "2013-02-26"
content: |
<p>The last few months have seen a huge increase of activity on the CMF (we seem to not have written many news, but those following the github projects will have seen it). Both Jackalope and PHPCR-ODM and the CMF bundles got new features and tons of issues fixed. And the documentation is starting to take shape, but can still use a lot of improvement.</p>
<p>With all this activity, it will be hard to draw the line for a 1.0 release, but nonetheless we need to do it. We built a <a href="https://github.com/symfony-cmf/symfony-cmf/wiki/Release-1.0">release plan</a> that wants to stabilize from the bottom up. We start with PHPCR and phpcr-utils, then go to Jackalope and its transports, then the Doctrine PHPCR-ODM and finally the Symfony2 CMF bundles. We created milestones in the PHPCR / Jackalope / PHPCR-ODM space for now. We hope to get through them until beginning of April, and should probably start version 1.0 milestones for the Symfony2 bundles mid of March and focus on the needed pieces in April.</p>
<p>The scope of features we get will depend on the contributions by everybody. But on the other hand, there is no problem adding new features soon afterwards and frequently tagging new versions - as long as we do not need to break backwards compatibility. One important focus is thus to tackle those problems that could require BC breaks so we can get them over before going to a stable release.</p>
getstarted:
name: "get-started"
title: "Get Started"
Expand All @@ -227,13 +239,13 @@ static:
Want to get started with the project? The best way to get your feet wet is follow the standard edition
<a href="http://symfony.com/doc/master/cmf/getting-started/installing-symfony-cmf.html">installation instructions</a>.
</p>
<p>
If you have further questions or need help getting started, visit our <a href="http://symfony.com/doc/master/cmf/index.html">documentation</a>
page or contact us in our <a href="irc://freenode/#symfony-cmf">IRC channel</a>. There is almost always someone around happy
to help you get started!
</p>
getinvolved:
name: "get-involved"
title: "Get Involved"
Expand Down

0 comments on commit a980d2b

Please sign in to comment.