Skip to content

Proposing unstable upgrade changes #8625

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 12, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 22 additions & 24 deletions setup/unstable_versions.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,54 +7,52 @@ they are released as stable versions.
Creating a New Project Based on an Unstable Symfony Version
-----------------------------------------------------------

Suppose that Symfony 2.7 version hasn't been released yet and you want to create
Suppose that the Symfony 4.0 version hasn't been released yet and you want to create
a new project to test its features. First, :doc:`install the Composer </setup/composer>`
package manager. Then, open a command console, enter your project's directory and
execute the following command:

.. code-block:: terminal

$ composer create-project symfony/framework-standard-edition my_project "2.7.*" --stability=dev
# Download the latest beta version
$ composer create-project symfony/skeleton my_project "4.0.*" -s=beta

# Download the absolute latest commit
$ composer create-project symfony/skeleton my_project "4.0.*" -s=dev

Once the command finishes its execution, you'll have a new Symfony project created
in the ``my_project/`` directory and based on the most recent code found in the
``2.7`` branch.

If you want to test a beta version, use ``beta`` as the value of the ``stability``
option:

.. code-block:: terminal

$ composer create-project symfony/framework-standard-edition my_project "2.7.*" --stability=beta
in the ``my_project/`` directory.

Upgrading your Project to an Unstable Symfony Version
-----------------------------------------------------

Suppose again that Symfony 2.7 hasn't been released yet and you want to upgrade
Suppose again that Symfony 4.0 hasn't been released yet and you want to upgrade
an existing application to test that your project works with it.

First, open the ``composer.json`` file located in the root directory of your
project. Then, edit the value of the version defined for the ``symfony/symfony``
dependency as follows:
project. Then, edit the value of all of the ``symfony/*`` libraries to the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a bit tricky as, for example, the release cycle of MonologBundle or SwiftmailerBundle (as well as the polyfill libraries) is independent from the framework's release cycle

new version and change your ``minimum-stability`` to ``beta``:

.. code-block:: json
.. code-block:: diff

{
"require": {
"symfony/symfony" : "2.7.*@dev"
}
+ "symfony/framework-bundle": "^4.0",
+ "symfony/finder": "^4.0",
"...": "..."
},
+ "minimum-stability": "beta"
}

Finally, open a command console, enter your project directory and execute the
following command to update your project dependencies:
You can also use set ``minimum-stability`` to ``dev``, or omit this line
entirely, and opt into your stability on each package by using constraints
like ``4.0.*@beta``.

.. code-block:: terminal
Finally, from a terminal, update your project's dependencies:

$ composer update symfony/symfony
.. code-block:: terminal

If you prefer to test a Symfony beta version, replace the ``"2.7.*@dev"`` constraint
by ``"2.7.0-beta1"`` to install a specific beta number or ``2.7.*@beta`` to get
the most recent beta version.
$ composer update

After upgrading the Symfony version, read the :ref:`Symfony Upgrading Guide <upgrade-major-symfony-deprecations>`
to learn how you should proceed to update your application's code in case the new
Expand Down