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/3311897`
➤ *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, located in Portland, OR:wave::skin-tone-3:
Sarah Corbine Hello, Sarah in Wisconsin. :pikachu_wave: (edited)
penyaskito Christian located in Seville, Spain. Interested on being up to date with what’s going on on the initiative and hoping I can help (classic post-DrupalCon enthusiasm)
eporama (he/him) Erik in Boston area :blob_wave:
Björn Brala (bbrala) Oh late hi!
quietone Hi
Ilcho Vuchkov (vuil) Ilcho Vuchkov, follow the updates…
Vighnesh Sadagopal hey:wave::skin-tone-3:  Vighneshh, India
Fathima Asmat Fathima from London, UK, sorry late appearance this time :wave:
wimleers (he/him) :wave:
Kristen Pol (she/her) Kristen, California, catching up late

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

hestenet (he/him) Could we have a summary of the major milestones (so not at issue level necessarily, but at conceptual level) between now and stable?
hestenet (he/him) ^^ And similarly, a summary of key blocking areas - and/or very nice to haves?
eporama (he/him) I have a question about per-table database prefixing. I see many tickets about warnings that it will be erroring in D10, but can’t see if it actually does.(To be fair, I haven’t actually tried it in beta1 either…) (edited)
Gábor Hojtsy (he/him) @hestenet (he/him) I think those two are the same, so 3️⃣ should be good? 🙂
hestenet (he/him) ++ thank you

2️⃣ :rocket: Since the last meeting, Drupal 9.5.0-beta1 and 10.0.0-beta1 were both released! Thanks all for the great work that went into these! (edited) 

Gábor Hojtsy (he/him) https://www.drupal.org/project/drupal/releases/10.0.0-beta1
Gábor Hojtsy (he/him) https://www.drupal.org/project/drupal/releases/9.5.0-beta1
Gábor Hojtsy (he/him) @catch @xjm #3118149: [meta] Requirements for tagging Drupal 10.0.0-beta1 is left open, should we close it or are there things to move elsewhere? As per the last comment from @catch it needs organization into release candidate blockers
catch @Gábor Hojtsy (he/him) yeah we need to shift some issues over to the rc list. PHP 8.2 and Symfony 6.2 are the obvious ones. Probably some 'should haves' amongst the rest.
catch @Gábor Hojtsy (he/him) finally got to it and closed the issue #3118149: [meta] Requirements for tagging Drupal 10.0.0-beta1
andypost 8.2 tests still fail (~30 ) https://www.drupal.org/pift-ci-job/2484518remaining fixes are[#3309748]

3️⃣ Next steps to release, what are the requirements

Gábor Hojtsy (he/him) Raised by @hestenet (he/him)
Gábor Hojtsy (he/him) #3304303: Drupal 10.0.0 requirements is the issue where these are collected
Gábor Hojtsy (he/him) it includes a link to issues tagged with “Drupal 10 RC blocker” https://www.drupal.org/project/issues/search?issue_tags=Drupal%2010%20rc...
hestenet (he/him) It sounds like people could help work on release notes and release highlights
hestenet (he/him) And the deprecated/obsolete module documentation.
hestenet (he/him) The rc blocker list of issues is small (in terms of count) but I'm not sure how tricky this test update work will be: https://www.drupal.org/project/issues/search?issue_tags=Drupal%2010%20rc...
Gábor Hojtsy (he/him) @hestenet (he/him) some issues may move from the beta task list to RC blockers, as per @catch’s comment there
Björn Brala (bbrala) Think the tests shouldn't be so hard. There was weirdness when they moved put with the whole composer fascade stuff. I'll use part of my time there.
catch PHP 8.2 and Symfony 6.2 should both be on there.
wimleers (he/him) I’m working on the ckeditor part of #3311367: Fix "Unknown themes: classy" error in the tests#comment-14709227 — on the verge of being green!
wimleers (he/him) @catch Can you tag the relevant PHP 8.2 and Symfony 6.2 issues then? :crossed_fingers: :pray:
catch @wimleers (he/him) have tagged both metas.
Gábor Hojtsy (he/him) I added them to the meta earlier today but was not sure about the tag vs the meta.
catch For the beta I was mostly using the meta, but I think other people were using the tag. I think the tag is mostly useful for tagging sub-issues of issues in the meta (like a specific, blocking, PHP 8.2 issue), or something like a regression/upgrade path bug that comes up. However it's confusing having two places to check/maintain.

4️⃣ Database prefixing, are the warnings really errors in Drupal 10?

Gábor Hojtsy (he/him) Raised by @eporama (he/him)
Gábor Hojtsy (he/him) #3106531: Notify in Status Report that per-table database prefixes are no longer supported, and will throw errors in Drupal 10.0
eporama (he/him) And as I typed, I wonder if maybe it’s just #3124382: Remove per-table prefixing (can’t see how I missed that :confused:) (edited)
eporama (he/him) Okay, this seems to be the final word:The per-table prefixing is removed in D10. A number of class variables and method are deprecated in D10.0 and will be removed in D11.0.Hence why the description seems to mention D11 alot.
wimleers (he/him) That makes sense.
wimleers (he/him) I’d swear this happened a long time ago, and looks like it indeed did…
wimleers (he/him) over a year ago to be exact: #3106531: Notify in Status Report that per-table database prefixes are no longer supported, and will throw errors in Drupal 10.0#comment-14211487

5️⃣ Ok this was a super quiet meeting, see you next week! 🙂

Comments

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

gábor hojtsy’s picture

Issue summary: View changes

gábor hojtsy’s picture

Issue summary: View changes

Saving notes. Thanks all!

gábor hojtsy’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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