-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Switch to Symfony 5 #6552
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
Comments
Symfony 4 require PHP 7.1, it sounds huge drop of PHP support. |
I would guess that you can still use composer 1.x for old php versions and composer 2.x for more modern ones. |
Another thing that will come: native color support on windows 10 for PHP 7.2+, as soon as symfony/console supports them (which is on my TODO-list for 3.4) |
Are there any plans on when to do a Composer 2 and what target environment it would have? I would volunteer to help with the migration, if help is needed. The migration could also be a source of tasks for the SymfonyCon hackday, maybe. |
@derrabus Composer is already compatible with Symfony 3 when using it as a library. What is impacted by this task is the phar, which requires being compatible with PHP 5.3 currently, and so cannot use Symfony 3 (which requires 5.5.9+) |
I think Composer 2.0 could safely drop support for PHP < 5.6, at the very least. Since even WordPress has been nagging users to upgrade to at least PHP 5.6 for a while now: https://wordpress.org/news/2019/04/minimum-php-version-update/ |
As composer 2.3 targets PHP 7.2+ Symfony 5 components could be used right ? Is the title outdated or is there a reason for Symfony 3 ? |
@BafS the title was not updated since 2017. |
I realized that @stof :) but as I saw some activity here I was wondering if it is intentional or if Symfony 5 could be a possibility |
@BafS the newest discussion happened in #9303 (comment) |
Ah great, thanks ! |
Uh oh!
There was an error while loading. Please reload this page.
Just a list of things that would be good to have once we can switch to Symfony 3 (or 5..), as a reminder only.
The text was updated successfully, but these errors were encountered: