Drupal 10 readiness meeting / 5 September 2022 [#3306651]

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

Hello and welcome to this Drupal 10 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 10 upgrade of their sites are also welcome.
➤ Now happens every 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/3306651`
➤ *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.

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

hestenet (he/him)	Tim from the Drupal Association, in Portland, OR - kicking off the threads today.
andypost	Andy, contributor
Warped	Dave in Chicago. Still lurking and watching. But since it is a holiday in the US, I figured I wouldn't leave it at just you two.
diqidoq	Hello, diqidoq here. Sorry for being late. Had a longer oversea call to manage.
longwave	Dave, UK
Gábor Hojtsy (he/him)	Late joiner this week, Gábor from Hungary.
catch	Nat, late.
quietone	Hi
kimb0	Kim :wave:
Libbna	Hey, Libbna here from India. :wave:
Vighnesh Sadagopal	Hey, Vighneshh from India :wave:
omkar-pd	Hello :wave:
shaal	Hello :minion:(reading everything after the holiday)
Kristen Pol (she/her)	Kristen, California, catching up
saschaeggi	Sascha, late :bird:
Jatin Gupta	Hey, Jatin from India :wave:
Ilcho Vuchkov (vuil)	Ilcho Vuchkov, Bulgaria

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we'll open threads for them as appropriateThreads moving slow - or your requested thread hasn't been added yet? Feel free to add your own thread to the bottom of the list. (edited)

Kristen Pol (she/her)	Wow! First time I haven't see any topics suggested, I think…As far as I understand, there is no remote aspect of DrupalCon contribution but was wanting to doublecheck that for this initiative
xjm	Probably because it was Labor Day 🙂 I personally was offline the whole day

2️⃣ :partying_face: RDF module and QuickEdit are now removed from Drupal 10, thanks to all who helped!

Spokje

Sisyphus is starting to feel lonely and hopes for a new round of Quick Edit-like deprecations/removals...

3️⃣ . 1️⃣ Beta must have: PHP 8.2 support needs work #3283358: [META] Make Drupal 9/10 compatible with PHP 8.2 (edited)

hestenet (he/him)	The DA will be trying to have the latest 8.2 RC container up and running tomorrow per - #3283449: Create a DrupalCI Environment for PHP 8.2 (edited)
andypost	It fixes few tests on 8.2 and mostly ready #3299828: Stop storing Settings singleton in object properties
andypost	2nd blocker #3298731: Using ConstraintViolation::$arrayPropertyPath bugs on PHP 8.2 mostly ready
andypost	3rd blocker #2531564: Fix leaky and brittle container serialization solution
andypost	and the last (fgotten) [#3274474]basically it fixes ~ few hundreds tests
andypost	There's also some remaining ~100 tests but I bet 70% will be fixed with container issueI mean the patch-testing issue https://www.drupal.org/pift-ci-job/2463136 (edited)
Kristen Pol (she/her)	Should the first issue be tagged with PHP 8.2 and/or Drupal 10 beta should-have?
andypost	Yes
Kristen Pol (she/her)	Done
hestenet (he/him)	8.2 environment is now updated to rc1.
hestenet (he/him)	#3283449: Create a DrupalCI Environment for PHP 8.2#comment-14683035
andypost	queued reroll of cumulative patch https://www.drupal.org/pift-ci-job/2469802
andypost	Btw 23 failed tests left
andypost	And one more I forget to mention - blocker #2839195: Add a method to access the original property

3️⃣ . 2️⃣ Beta must have: Symfony 6.2 is as good as it can be ATM for the beta, thanks all. #3284422: [META] Symfony 6.2 compatibility (edited)

andypost	there's RTBC [#3307736]and it needs to file new issue for #43 (and maybe for #5)
diqidoq	@andypost are you referring to the comments #5 and #43 in #3307736 ? (edited)
andypost	Refering to the topic issue #3284422 (edited)
diqidoq	Sorry wong issue id typed, yes that was the issue id I was asking about
andypost	basically there's one big patch which needs 1 more issue to split
Gábor Hojtsy (he/him)	@hestenet (he/him) oops, I posted the wrong issue ID in the agenda, can you fix it above? Thx
hestenet (he/him)	Oh sure.

3️⃣ . 3️⃣ Beta must have: State of CKEditor 5 support #3238333: Roadmap to CKEditor 5 stable in Drupal 9

andypost	The link is #3238333: Roadmap to CKEditor 5 stable in Drupal 9
Kristen Pol (she/her)	The summary is weird to me… there are green checkboxes indicating things are fine I suppose but have “currently none” underneath them… ?
Kristen Pol (she/her)	Oh… no outstanding issues?
Kristen Pol (she/her)	Test coverage has no check mark but says currently none
xjm	Probably just a typo

3️⃣ . 4️⃣ Beta must have: what to do with asset build step? ^^ Your input requested

andypost	There's issue with missed date #3278415: Remove usages of the JavaScript ES6 build step, the build step itself, and associated dev dependencies
andypost	looks the question more is about #3238497: What to do with assets build step? (edited)
longwave	I am +1 to keeping it and repurposing it for #3302755: On-the-fly JavaScript minification
Gábor Hojtsy (he/him)	That was I think the proposal last week as well but it did not seem conclusive.
catch	I'm +1 to keeping it and using it for minification as well. Only question for me is that can we easily do the repurposing in a minor release, feels like we ought to be able to though especially since we've already got the .es6.js file pattern in core.
longwave	yeah it might feel cleaner if the source files are .js instead of .es6.js and then we minify to *.min.js - but it's also quite late to get that into 10.0.x :confused:
catch	Yeah also renaming the files in library definitions would be a pain, we'd need some kind of libraries override treatment.
nod_	ideally we'd find an "out of band" solution that automate the minification and doesn't impact contributors. I mean we could minify "in place" and create the sourcemaps for debugging during the release or something
nod_	so the .js file holds the source during dev, and when it's a release the .js is the minified file, the source can still be available in the .map.js file generated next to it
longwave	the thing here is what constitutes a release? it's just a git tag that can be checked out, so the minified files have to make it into the repo somehow? (and then be reverted again post release?)
nod_	ah right, composer points to the repo directly
catch	We could probably do it with a release branch.
nod_	I just don't want to go back to having both version in the source repo/branch
catch	10.x-releases ahh but they still can't have the same name then easily.
nod_	release branch sounds good as long as it's fully automated based on a commit/tag
catch	If we make a new release branch from scratch every tag it might work.
nod_	if we switch to calling the dev branch "main" that could work no?
catch	We'd still need to be able to merge changes back to branches.
catch	It'd need to be something like checkout -b 10.0.0-release; run build stuff; tag 10.0.0
catch	That way you never have to merge anything into a release branchm
nod_	sounds reasonable to me
longwave	ideally this process would also be available to contrib
catch	We could move the version number change/back to dev commits there too.
nod_	that'll suck a bit for issue forks with all those new branches but maybe there is a way to filter them on fork?
longwave	it does sound more complicated but maybe a release branch is worthwhile

3️⃣ . 5️⃣ Beta must have: remove popperjs from Drupal 10#3301545: Remove popperjs from Drupal 10

Kristen Pol (she/her)

It's done! :tada:

4️⃣ Help draft the release notes for the Drupal 10 beta! #3306660: Draft release notes for 10.0.0-beta1^^Yes - we mean you! 🙂

5️⃣ Remote contribution during DrupalConThere are not official remote contribution spaces set up as part of DrupalConHowever, that doesn't mean that people can't contribute while remote, and coordinate with the people in the contribution rooms 🙂 Does anyone remote have the time/energy to try and coordinate? Or shall we assume folks will play it by ear here in Slack? (edited)

Kristen Pol (she/her)	True… just wasn't sure if anyone had planned to do that… I don't think I have time to organize anything
Gábor Hojtsy (he/him)	Yup, there is no official remote contribution organized, but that should not stop people to organize something.