Meeting will happen in #d9readiness on drupal.slack.com.

Hello and welcome to this Drupal 9 readiness meeting!

This meeting:
➤ Is for core and contributed project developers as well as people who have integrations and services related to core. Site developers who want to stay in the know to keep up-to-date for the easiest Drupal 9 upgrade of their sites are also welcome.
➤ Usually happens every other Monday at 18:00 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to: `https://www.drupal.org/project/drupal/issues/3072777`
➤*Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

Moderated By: mikelutz

0️⃣ Who is here today? Comment in the thread below to introduce yourself.

greg.1.anderson Greg Anderson, Pantheon, lurking
tedbow hi, Ted from Ithaca, Ny
Alona Oneill Alona, Hook42, SF. Taking notes for company weekly Drupal Core Initiative Meetings Recap blog
mixologic Mixologic. D.A., Kinda on vacation, but in front of my computer anyhow.
Nick Wilde Nick, he/him, Taoti, aka keeping up on this for work as well as contrib maintainer.
mikelutz Mike - Core migrate sub-system maintainer and guest moderator.
larowlan Lee - collector of air-dried corn
catch Nat, core committer.
lendude Len from Amsterdam, lurking

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.

tedbow since @greg.1.anderson(I think involved with composer initiative) wondering if composer initiative folks are aware of #3005229: Provide optional support for using composer.json for dependency metadata and that it could happen in 8 cycle
greg.1.anderson Yes, aware of that.
Mile23 Work continues apace on #3057420: [meta] How to deprecate Simpletest with minimal disruption

2️⃣ Symfony development updates

mikelutz @mixologic did I break something here? https://www.drupal.org/pift-ci-job/1381697
mixologic As in why is it still queueing?
mikelutz lol, yeah.
mixologic oh, I know why. dang. When I added the stable php 7.3 container to the matrix, I didnt update the jenkins job to expect it. Thus any jobs using that are all queueing, retrying.
mikelutz I suspected it was something to do with that 7.3 stable container. I’d never queued a job up with it before. :slightly_smiling_face:
mixologic I just fixed it though, so they should all start flowing over to dispatcher now.
mikelutz So, Symfony updates. We are now have a patch to test against SF4.4-dev at #2976394: Allow Symfony 4.4 to be installed in Drupal 8. There’s 2 failures there, one due to a wording change in a constraint violation message, which has an issue open, and one failure in a Functional Javascript test that for the life of me I can’t get to fail locally. Otherwise, as part of that patch we do suppress many deprecation errors that are emitted as of SF 4.4.
mixologic Functional Javascript might be due to the age of the chromedriver container in drupalci
mikelutz Possibly, though it’s odd that it’s just one test. I did make a halfhearted attempt to switch to an old chromedriver, but I couldn’t get it to take.
mikelutz One of the bigger deprecations we now suppress is now on return typehinting. Symfony’s classloader now seems to scan through annotations and anywhere it finds a return typehint in an annotation, throws a deprecation error if an extending or implementing class doesn’t use that as a php return typehint. There may be other ways around it too, but it’s interesting and going to be tricky.
mixologic You can try to get it to fail using a local drupalci testbot: instructions here: https://www.drupal.org/drupalorg/docs/drupal-ci/running-drupalci-locally
mikelutz It’s also problematic when the docblock returns ‘object’ which can’t be a php return typehint. The feature was only added in the past week or so, so I’m sure there’s cleanup to be done. I’ll be keeping an eye on it, and maybe contributing as I have time.
mikelutz Thanks, @mixologic I’ll give that a shot.
mikelutz Also on the Symfony front, we got stringable constraint violation messages to land in Symfony 4.4. So we reverted the workaround we originally committed in #3029540: [Symfony 4] Sub class \Symfony\Component\Validator\ConstraintViolation and use that in \Drupal\Core\TypedData\Validation\ExecutionContext::addViolation()
mikelutz @mixologic Well, that definitely fails locally with drupalci, though I’m not sure I’m any closer to debugging the actual issue, lol.

3️⃣ Composer initiative issues affecting D8 and D9

mikelutz #3005229: Provide optional support for using composer.json for dependency metadata
greg.1.anderson So, the things happening in the Core Composer Initiative are:
- #3067645: Add core scaffold assets to drupal/core's composer.json extra field: add scaffold assets to drupal/core
- #3013210: Add drupal/core-filesecurity component for writing htaccess files: add drupal/core-filesecurity component
The later might have some deprecations, but I don't think that either of those issues have any impact for this meeting. Just dropping them here for visibility in case it sparks any thoughts.
tedbow @greg.1.anderson ok just wanted to make sure we aren’t doing anything in 3005229 that would conflict with any future plans; though this issue has a long way to go
greg.1.anderson I'll review that issue again but I think it's all cool and compatible
tedbow great. thanks
greg.1.anderson @mixologic is all over that issue already so cool cool
tedbow yep

4️⃣ Simpletest deprecation process

mikelutz #3057420: [meta] How to deprecate Simpletest with minimal disruption
larowlan we’re finally moving on this front :bullettrain_front:
lendude Yeah great to see this moving

5️⃣ Anything else we want to discuss?

6️⃣ Thanks for coming, please continue the discussion in the threads above.

Comments

Gábor Hojtsy created an issue. See original summary.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia commented
Issue summary: View changes

Gábor Hojtsy credited Mile23.

Gábor Hojtsy credited Mixologic.

Gábor Hojtsy credited alonaoneill.

Gábor Hojtsy credited greg.1.anderson.

Gábor Hojtsy credited larowlan.

Gábor Hojtsy credited mikelutz.

Gábor Hojtsy credited tedbow.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia commented
Issue summary: View changes
Status: Active » Fixed

Thanks everyone! See you on the next meeting on September 2nd: #3076507: Drupal 9 readiness meeting / 2 September 2019

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.