Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Follow-up to #2712647: Update Symfony components to ~3.2 since 3.2.0 is already out. Symfony 3.2.0 was released on November 30, 2016. See #2712647: Update Symfony components to ~3.2 for the current status of the issue.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#37 | interdiff.txt | 3.02 KB | slasher13 |
#37 | 2831757-37.patch | 91.38 KB | slasher13 |
#34 | interdiff.txt | 1.91 KB | slasher13 |
#34 | 2831757-34.patch | 95.63 KB | slasher13 |
#33 | 2831757-33.patch | 93.93 KB | slasher13 |
Comments
Comment #2
Wim Leers#2712647: Update Symfony components to ~3.2 is in.
Comment #3
Wim LeersComment #4
Wim LeersComment #5
Wim LeersCR will need to point to https://github.com/symfony/symfony/blob/master/UPGRADE-3.2.md. Or perhaps we just want to update https://www.drupal.org/node/2743809 ?
Comment #6
klausi3.2 already contains the dom-crawler and http-foundation fixes, so we can use ~3.2. I hate the "~" operator because nobody can read it, but I hate inconsistency even more :-D
Comment #7
Wim Leershehe :)
Comment #10
jibranThe patch is missing
symfony/css-selector
.Comment #11
slasher13patch on top of https://www.drupal.org/node/2712647#comment-11808905
and https://www.drupal.org/node/2573807#comment-11810963, but why isn't the expires header set?
Comment #13
slasher13changes from https://github.com/symfony/http-foundation/commit/295423690c79e35a59d2ae...
Comment #14
jibranDo we have to update these files?
Comment #15
jibranDo we have to update these files?
Comment #16
slasher13In
we have only the changes from https://www.drupal.org/node/2712647.
Should I merge this into https://www.drupal.org/node/2712647 without https://www.drupal.org/node/2573807?
Comment #17
DamienMcKennaLooking at it, it doesn't seem like #2573807 has any connection to this? I'd vote to merge this back into #2712647.
Comment #18
slasher13Comment #19
slasher13update to symfony 3.2.2
Comment #21
slasher13fix wrong merge from #19
Comment #22
jibranI think we can use https://www.drupal.org/node/2743809 as a change record for this issue and 3.1 issue has no momentum so I'm going to be bold and set it to RTBC. We can close 3.1 one as a duplicate.
Comment #23
naveenvalechawould you update the CR including the changes in 3.2 accordingly
//Naveen
Comment #24
catch@jibran the 3.1 issue has no momentum because it makes Drupal incompatible with drush, see https://github.com/drush-ops/drush/pull/2477
Comment #26
slasher13re-roll
Comment #27
slasher13Back to RTBC as #22
Comment #28
alexpottThis is at least postponed on #2843828: \Drupal\Core\DrupalKernel::initializeSettings() can result in moving the autoloader position and it is probably postponed on working out a way forward for https://github.com/drush-ops/drush/pull/2477
Comment #29
catchDiscussed this a bit with @alexpott and @xjm, at the moment we think we should commit this early in 8.4.x - this gives additional time to keep rolling back and re-committing the update as new things are uncovered, as well as more time to determine if there needs to be a new minor or major drush release.
Comment #30
TJacksonVA CreditAttribution: TJacksonVA commentedAre there any changes/additions from Symfony 2.8 to Symfony 3.2 or 3.3 that Drupal 8.x module developers would find important or useful? If so, it may be a mistake to wait until Drupal 8.4.x to implement the Symfony upgrade.
Comment #31
pounardAs soon as you use external components, it's safe to say upgrading to 3.2 is a plus. I personally work with many libraries where I do need 3.2 - for a site to come in a few months, I was awaiting for Drupal 8.3 to bring Symfony 3.2 and some other fixes along to play well with it.
Comment #33
slasher13re-roll
Comment #34
slasher13Comment #37
slasher13Comment #39
slasher13Comment #40
xjmThis should either be postponed on the 3.1 update, or merged into it. See the summary of #2712647: Update Symfony components to ~3.2. We need to allow time for contrib and drush to fully support Symfony 3.
Comment #41
slasher13see https://www.drupal.org/node/2712647#comment-11901458