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 19: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/3096685`
➤*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.

:zero: Who is here today? Comment in the thread below to introduce yourself.

Alona Oneill Alona from San Francisco. Taking notes for blog
webchick webchick from :canada:
Gábor Hojtsy (he/him) Gábor, D9 coordinator
mikelutz Hello all.
mradcliffe Matthew (he/him) from Columbus.
shaal Ofer Shaal, Umami maintainer, from Florida :sunglasses:
greg.1.anderson @greg.1.anderson SF / Composer / Drush / Pantheon / Lurker.
alexpott Hullo alex from london - mostly afk but following along

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

mradcliffe Regarding #3094468: [plan] Update core JavaScript (and CSS) dependencies prior to 9.0.0-beta1, I think that only farbtastic and jquery.cookie are concerns for 9.0.0-alpha1. The other things can be updated as the issue mentions in 9.0.0-beta1.

:two: Drupal 9.0.0-alpha1 release blockers according to #2608062: [META] Requirements for tagging Drupal 9.0.0-alpha1 (edited) 

:two: .:one: Symfony 4.4.0 compatibility

Gábor Hojtsy (he/him) #3088754: Update to Drupal 9 to Symfony 4.4.0
Gábor Hojtsy (he/him) @mikelutz has been working on this
Gábor Hojtsy (he/him) looks like down to dependencies’ dependencies questions :)
mikelutz There is only one change we needed to make from the beta2 compatibility to be compatible with 4.4.0, and it was a test update.
greg.1.anderson Drush should be fine with these changes, but we'll keep an eye on it.
mikelutz Looks like @catch and @alexpott will allow committing using the explicit dependency method, so I guess I need to re-roll that with the test fix.
mikelutz Nope, I read wrong again..
alexpott :slightly_smiling_face: I think we should add a follow-up issue to discuss this again before the beta is released
mikelutz I gave three options, @catch said he was good with 1 or 3, and alex said to use #2. So I quit until either more committers weigh in or the two there have consensus.
alexpott Fair enough
alexpott I’ll try to catch up with catch about this later or tomorrow
mikelutz Or even consensus on what to commit now, and kick the final decision to a follow-up.
mikelutz Sounds good.
Gábor Hojtsy (he/him) :thumbsup:
catch I'm pro kicking the final decision to a followup.
mikelutz @catch, Then all I need is you and @alexpott to agree on the interim solution, and I’ll roll it up.
alexpott Let’s do nothing have real dependencies and let composer get you sf5 things if that’s what it resolves to (edited)
mikelutz That probably makes the most sense if we are kicking the decision down the road.
mikelutz Wrapping up a meeting, but I’ll post it shortly.

:two: .:two: Forking jQuery UI into Drupal 9

Gábor Hojtsy (he/him) #3087685: Remove deprecated jQuery UI components and fork remaining source code into core
Gábor Hojtsy (he/him) @zrpnr and @lauriii have been working on this
Gábor Hojtsy (he/him) it was briefly RTBC by @catch, not entirely clear to me what is outstanding now, the remaining tasks list in the issue summary does not give any leads
zrpnr I can update the IS, the last remaining issues were whitespace in one of the copied source files, and opening a PR in d8githooks to check that these files have been minified correctly if there were any changes. Those are both done, and the other questions raised in this issue all have follow-ups now (edited)
Gábor Hojtsy (he/him) great, thanks — do we hope @lauriii RTBCs it, or @catch? :slightly_smiling_face: or we need more eyes on it? (edited)
zrpnr the last review was from lauri, but the whitespace change could be reviewed by anyone. He is probably the best to look at the new js written for the d8githooks PR, it is similar to the es6 check. I'm not sure who would need to actually review the d8githooks PR!
zrpnr https://github.com/alexpott/d8githooks/issues/28
Gábor Hojtsy (he/him) @alexpott would merge it in ^^^ :slightly_smiling_face:

:two:.:three: Using “current” in update URLs

Gábor Hojtsy (he/him) #3074993: Use "current" in update URLs instead of CORE_COMPATIBILITY to retrieve all future updates
Gábor Hojtsy (he/him) @tedbow has been working on this
greg.1.anderson The new changes are a little awkward for the Drush pm-* commands, which are not well maintained. If anyone feels like polishing the rough edges for non-Composer / Drush pm-* users, I'd be willing to mentor.

:two:.:four: The above three are the must haves, any other alpha-blockers people want to raise?

mradcliffe Regarding #3094468: [plan] Update core JavaScript (and CSS) dependencies prior to 9.0.0-beta1, I think that only farbtastic and jquery.cookie are concerns for 9.0.0-alpha1. The other things can be updated as the issue mentions in 9.0.0-beta1.
Gábor Hojtsy (he/him) @mradcliffe should those be broken out to their own issue then?
mradcliffe farbtastic and jquery.cookie are unmaintained/unsupported and could be security concerns.
mradcliffe We have one for jquery.cookie, and I wrote a patch :yay:
mradcliffe I don't know about farbtastic, but it's a read-only github repo. (forked for drupal's use) so if we want to ship with that, that seems fine.
mradcliffe But there would be no way to push changes upstream if something was wrong with that library.
Gábor Hojtsy (he/him) well, similar to the jQuery UI fork we have(?)
mradcliffe Yes, I think so.
mradcliffe ugh, realized I had been working on some comments about js-cookie 3.0.0 vs js-cookies 2.2.1 and I never finished and closed the browser tab they were in a long time ago :disappointed:
mradcliffe I don't know if these are truly alpha blockers, but still would block beta like the rest of the javascript dependencies.
mradcliffe @Gábor Hojtsy (he/him)
Gábor Hojtsy (he/him) @mradcliffe my understanding was that these are considered beta blocker as per the issue, but if there are disruptive updates, those should be discussed with release managers :slightly_smiling_face:
mradcliffe I guess with a bc layer it wouldn't be disruptive.

:three: “New” contrib deprecation tooling especially useful for contribution events

Gábor Hojtsy (he/him) officially launched a deprecation browser on dev.acquia.com 5 days ago :slightly_smiling_face: http://hojtsy.hu/blog/2019-nov-20/introducing-drupal-9-deprecation-statu...
Gábor Hojtsy (he/him) this uses the drupal.org phpstan data
Gábor Hojtsy (he/him) also has some charts tracking core @deprecated usage and contrib deprecations by various angles at https://dev.acquia.com/drupal9/deprecation_status/graphs

:four: Gaps in deprecation testing tools (JS, libraries, twig, global constants)

Gábor Hojtsy (he/him) I should have a META issue to track all of them at once place really
Gábor Hojtsy (he/him) give me a couple minutes :smile:
Gábor Hojtsy (he/him) Issues gathered now in #3096678: [META] Missing deprecation testing coverage
Gábor Hojtsy (he/him) @mglaman had proof of concept code that hardcoded core constants, I think that would still be better than nothing, if someone can help salvage that and get it in :slightly_smiling_face:
Gábor Hojtsy (he/him) I think we hoped that we find people interested in filling these gaps by this point :slightly_smiling_face:
Gábor Hojtsy (he/him) the more visible we make the reports, the more pressing it is that there are some sizable holes in the reporting
mradcliffe I don't think we can use phpstan to test non-php files like JavaScript. There might be an existing eslint plugin. eslint can output junit.
Gábor Hojtsy (he/him) @mradcliffe yeah the idea was that drupal-check could merge the outputs and the result would be used altogether
mradcliffe Here's the issue on github - https://github.com/mglaman/drupal-check/issues/29
Gábor Hojtsy (he/him) yup :slightly_smiling_face:
Gábor Hojtsy (he/him) I opened the upgrade status counterpart but that is not the place to fix it in a first party way :slightly_smiling_face:

:five: Quiet meeting today :slightly_smiling_face: Thanks all for coming, see you around! See you in two weeks on what may be the last D9 meeting of the year :slightly_smiling_face: #3096685: Drupal 9 readiness meeting / 25 November 2019

Comments

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

gábor hojtsy’s picture

Issue summary: View changes

mikelutz credited webchick.

mikelutz’s picture

Issue summary: View changes

mikelutz’s picture

mikelutz credited shaal.

mikelutz’s picture

mikelutz’s picture

mikelutz’s picture

mikelutz credited alexpott.

mikelutz’s picture

mikelutz credited catch.

mikelutz’s picture

mikelutz’s picture

mikelutz’s picture

gábor hojtsy’s picture

Title: Drupal 9 readiness meeting / 9 December 2019 » Drupal 9 readiness meeting / 25 November 2019
Status: Active » Fixed
Parent issue: #3093746: Drupal 9 readiness meeting / 9 December 2019 » #3093743: Drupal 9 readiness meeting / 11 November 2019

Fix title and relationships given Nov 25 meeting log posted :) Thanks @mikelutz!

mikelutz’s picture

Status: Fixed » Closed (fixed)

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