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

Proposing unstable upgrade changes #8625

merged 2 commits into from
Nov 12, 2017

Conversation

weaverryan
Copy link
Member

This document - https://symfony.com/doc/master/setup/unstable_versions.html - now quite out-of-date:

  • We use symfony/skeleton
  • The user will now have many symfony/* dependencies, not just symfony/symfony.

It's a bit tricky, so I would appreciate a review.

Thanks!

Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

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

The proposed changes look great to me and I think everything is perfectly explained. Thanks for updating!

@weaverryan weaverryan added this to the 4.0 milestone Nov 12, 2017
@weaverryan weaverryan merged commit 357826f into master Nov 12, 2017
weaverryan added a commit that referenced this pull request Nov 12, 2017
This PR was squashed before being merged into the master branch (closes #8625).

Discussion
----------

Proposing unstable upgrade changes

This document - https://symfony.com/doc/master/setup/unstable_versions.html - now quite out-of-date:

* We use `symfony/skeleton`
* The user will now have many `symfony/*` dependencies, not just `symfony/symfony`.

It's a bit tricky,  so I would appreciate a review.

Thanks!

Commits
-------

357826f fixing
a37886a Proposing unstable upgrade changes
@wouterj wouterj deleted the weaverryan-patch-2 branch November 13, 2017 00:09
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants