@@ -7,54 +7,52 @@ they are released as stable versions.
77Creating a New Project Based on an Unstable Symfony Version
88-----------------------------------------------------------
99
10- Suppose that Symfony2.7 version hasn't been released yet and you want to create
10+ Suppose thatthe Symfony4.0 version hasn't been released yet and you want to create
1111a new project to test its features. First,:doc: `install the Composer </setup/composer >`
1212package manager. Then, open a command console, enter your project's directory and
1313execute the following command:
1414
1515..code-block ::terminal
1616
17- $ composer create-project symfony/framework-standard-edition my_project "2.7.*" --stability=dev
17+ # Download the latest beta version
18+ $ composer create-project symfony/skeleton my_project "4.0.*" -s=beta
19+
20+ # Download the absolute latest commit
21+ $ composer create-project symfony/skeleton my_project "4.0.*" -s=dev
1822
1923 Once the command finishes its execution, you'll have a new Symfony project created
20- in the ``my_project/ `` directory and based on the most recent code found in the
21- ``2.7 `` branch.
22-
23- If you want to test a beta version, use ``beta `` as the value of the ``stability ``
24- option:
25-
26- ..code-block ::terminal
27-
28- $ composer create-project symfony/framework-standard-edition my_project "2.7.*" --stability=beta
24+ in the ``my_project/ `` directory.
2925
3026Upgrading your Project to an Unstable Symfony Version
3127-----------------------------------------------------
3228
33- Suppose again that Symfony2.7 hasn't been released yet and you want to upgrade
29+ Suppose again that Symfony4.0 hasn't been released yet and you want to upgrade
3430an existing application to test that your project works with it.
3531
3632First, open the ``composer.json `` file located in the root directory of your
37- project. Then, edit the value ofthe version defined for the ``symfony/symfony ``
38- dependency as follows :
33+ project. Then, edit the value ofall of the ``symfony/* `` libraries to the
34+ new version and change your `` minimum-stability `` to `` beta `` :
3935
40- ..code-block ::json
36+ ..code-block ::diff
4137
4238 {
4339 "require": {
44- "symfony/symfony" :" 2.7.*@dev"
45- }
40+ + "symfony/framework-bundle": "^4.0",
41+ + "symfony/finder": "^4.0",
42+ "...": "..."
43+ },
44+ + "minimum-stability": "beta"
4645 }
4746
48- Finally, open a command console, enter your project directory and execute the
49- following command to update your project dependencies:
47+ You can also use set ``minimum-stability `` to ``dev ``, or omit this line
48+ entirely, and opt into your stability on each package by using constraints
49+ like ``4.0.*@beta ``.
5050
51- .. code-block :: terminal
51+ Finally, from a terminal, update your project's dependencies:
5252
53- $ composer update symfony/symfony
53+ .. code-block :: terminal
5454
55- If you prefer to test a Symfony beta version, replace the ``"2.7.*@dev" `` constraint
56- by ``"2.7.0-beta1" `` to install a specific beta number or ``2.7.*@beta `` to get
57- the most recent beta version.
55+ $ composer update
5856
5957 After upgrading the Symfony version, read the:ref: `Symfony Upgrading Guide <upgrade-major-symfony-deprecations >`
6058to learn how you should proceed to update your application's code in case the new