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/3051451`
➤*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: Gabor Hojtsy (he/him)

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

Gabor Hojtsy (he/him) Gábor core committer, D9 coordinator.
xjm xjm, release manager
Alona Oneill Alona, hook42, community developer. New to this
xjm @timplunkett (he/him) @bnjmnm here if you are interested :-)
shaal Ofer Shaal, Umami maintainer
Gabor Hojtsy (he/him) cc @catch, @mixologic, @mglaman, @mcdwayne, @berdir, @herczogzoltan, @chr.fritsch, @mikelutz
catch Nat. Core committer.
mglaman Matt. Drupal Checker thinger. Just got home from errands, here :slightly_smiling_face:
Nick Wilde Nick, he/him, Victoria BC :canada: most likely just lurking as normal
mikelutz Mike, deprecation drone. :slightly_smiling_face:
hotwebmatter Matt. he/him, Providence RI. Lurking since Global Contribution Week. Interested in helping but not sure how.
larowlan Lee, late but timezones
xjm You got a better picture of your plant!
larowlan Different plant...but yeah old one was 10 yrs old
berdir Berdir, deprecator of things. Was busy catching up on GoT :crossed_swords:
xjm Mīsio?
berdir @xjm not sure if I get that reference :slightly_smiling_face:
xjm @berdir "Protector" in High Valyrian :wink:
berdir @xjm ah, thought it would probably be that, yeah, good new username if I ever need one :wink: googling that finds some ...interesting fanfic :wink:
xjm I can only imagine

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

catch What do people think about a PHP 7.3 requirement for Drupal 9?
catch Also maybe
xjm I posted a few topics on the agenda node earlier
Gabor Hojtsy (he/him) @xjm posting those, CKEditor 5 would be part of one of those :slightly_smiling_face:
mglaman @Gabor Hojtsy (he/him) can you open a thread so I can post drupal-check phpstan updates?

2️⃣ Deprecation works. Entity.inc is being worked on by @berdir and @mikelutz, progress is summarised in

Gabor Hojtsy (he/him) various of these issues need reviews, help is welcome :slightly_smiling_face:
Gabor Hojtsy (he/him) I wanted to celebrate this win as part of this effort: :slightly_smiling_face:
Gabor Hojtsy (he/him) :high5:
mglaman Now we can deprecate the commerce replacement :stuck_out_tongue:
mglaman Also, @berdir if this helps vs spreadhseet
mikelutz Man, I wasted 4 minutes putting that spreadsheet together. :wink:
mglaman :smile:
Gabor Hojtsy (he/him) :smile:
xjm should we talk about the rule issues here or in their own thread?
Gabor Hojtsy (he/him) own
larowlan Berdir++ Mike++ please ping if you need issues unlocked..sorry for dropping the ball on one this week
mikelutz @larowlan++
berdir @mglaman must be really important to be listed 5x on that dashboard :wink:
mglaman :X I copied each NID from the spread sheet
berdir Oh no, so much to do. Wait a second...
mglaman maybe I double copied
mglaman :smile: yeah multiple rows had that nid, @berdir fixed
mikelutz heh, yeah some issues touched more than one of the methods. :slightly_smiling_face:
mikelutz I was all set to RTBC that one, @berdir but it needs a reroll.
berdir F5 :slightly_smiling_face:
berdir load by properties is also updated. now afk for a few minutes
berdir @mikelutz , confused by that. this issue already deprecates user_view() (and node_view() and comment_view() and taxonomy_term_view())
berdir and I'd suggest to just merge in user_delete() too into the entity_delete() issue, we did that for the load functions too
berdir just 5k more, and if we don't deprecate it, then we have to update it so it doesn't trigger deprecations..
larowlan @berdir on we're not using the `removed in {project}:{version}` format - did that change again?
larowlan same for
larowlan cc @mikelutz
berdir @larowlan technically, we did not change it *yet*. See
berdir but I'm still confused about that
larowlan @xjm ^ so we just leave as is and do them all in one pass with a phpcs rule?
xjm Yep
xjm Once we sort out these issues with the rule(s)
berdir I'm for example also confused that the format apparently doesn't validate "Drupal 9.0.0" vs "drupal:9.0.0" which seemed like one of the main things of the new format..
xjm _me also_
berdir well, at least we agree on that :slightly_smiling_face:
berdir @larowlan but yeah, was just about to ping you that 4 of these issues are now RTBC. I do think they are quite likely to conflict however, for example on the legacy test coverage, so we'll probably have to do a few rerolls. maybe you can get one or two in that don't conflict, and then we'll update the others
larowlan @berdir I think 3027178 has an issue on php5 (set back to NW)
mikelutz I missed that, I'll close my user view issue as a dupe then.
larowlan looks good and will wait for bot
larowlan what are the other 2 @berdir (I caught those two cause I'm following)
larowlan @xjm commiting to 8.8.x is fine during the freeze right?
xjm @larowlan Wrong slack but yep :slightly_smiling_face:
xjm we only freeze the dev branch for sec windows
larowlan @xjm oh, thought it was ok to ask here too - :+1:
larowlan @berdir ?
xjm @larowlan Oh totally, I thought you just accidentally asked in the wrong thread :slightly_smiling_face:
berdir they are on , still one duplicate through and I can't edit apparently cc @mglaman
mglaman lemme make edits global
larowlan sorry, I wasn't aware of that board - thanks
mglaman made the board public so anyone can add node IDs
mglaman @larowlan whipped it up today. in progress of preparing the “launch” of issue collection boards
larowlan ha privacy badger blocked ... after I visited contribkanban...reckons cross domain cookies are spying on me :eye:
larowlan couple of minor nits on sorry @mikelutz
berdir @larowlan see , I think that is fine on PHP 5, but I added a test run to be sure
berdir certainly a good idea to be certain about that after my double-mistake before the weekend :slightly_smiling_face:
larowlan looks good

3️⃣ Status and plan of major dependency upgrades (Symfony, CKEditor, Twig)

xjm So catch and I had a chat about this last week
xjm We have a meeting with the CKEDitor maintainers tomorrow morning
Gabor Hojtsy (he/him) I hope we can keep that meeting given @wimleers (he/him) sick :disappointed:
Gabor Hojtsy (he/him) I mean @wimleers (he/him) getting healthy is priority :slightly_smiling_face:
xjm What we'd _like_ to do is see if they can provide security coverage until the end of Nov. 2023. They said "until 2023" but did not specify a month. So we can ask at least.
xjm This is for CKE4
xjm Then if we do that, we start work on CKE5 as an experimental feature as early as possible
xjm Deprecate CKE4 and remove it for D10
xjm Nov. 2023 is also the earliest date we might have to EOL ~D8~ D9 due to Symfony 4, if we get stuck on 4 and not 5
xjm I'd actually like to keep looking into SF5 as long as possible though
xjm I recognize concerns that jumping two majors is more disruptive, but we're going to have to do so eventually
xjm either we jump from 3 to 5 for D9, or we jump from 4 to 6 for D10
mglaman I vote 3-5 for D9, if it’ll make future Drupal majors easier
xjm Yah that's how I feel too
mglaman of course I say that as someone not currently ensuring compatibility, but as a maintainer
xjm We have the opportunity beause they are releasing _right_ before us, at the end of the year
Gabor Hojtsy (he/him) the Seattle discussion we had, we discussed that making the D9 transition easy is *very important* — if we try to jump too big, then the promise of it being easy is not valid… if we can make this easy, then we can make more updates in shorter timeframes which are individually also easy
xjm So since we want to make core at least compatible anyway, see exactly what kind of disruption we'd be looking at
Gabor Hojtsy (he/him) also SF5 *may have* a higher PHP version requirement, may have strict typing introduced at more places, etc.
Gabor Hojtsy (he/him) (that is theoretics at this point)
mglaman (I cannot wait for that)
xjm @Gabor Hojtsy (he/him) I'm not saying 100% we must have SF5, but I'm saying we need to keep that open
Gabor Hojtsy (he/him) we need to define if we “keep it open” or “make it a priority”
xjm Our ecosystem can't handle having to EOL D9 in 2023 and D10 in 2025
Gabor Hojtsy (he/him) our ecosystem also cannot handle a painful upgrade :slightly_smiling_face:
xjm @Gabor Hojtsy (he/him) I want to put as muh work into it as possible becacuse we want D9 to be SF5-ccompatible anyway
Gabor Hojtsy (he/him) that IMHO means we put less work into other things that could make the upgrade simpler
Gabor Hojtsy (he/him) so long as we are aware of that, its fine
mglaman I see the SF3-> SF5 not being that painful. Or is the record otherwise?
mglaman it’s not like rewriting for Drupal core
xjm @Gabor Hojtsy (he/him) I don't think it needs to be the same people either
Gabor Hojtsy (he/him) @xjm I think its the same as running 3 major initiatives at once, there is going to be bottlenecks
xjm @Gabor Hojtsy (he/him) a lot of us were tied up in 8.7 :slightly_smiling_face:
xjm @Gabor Hojtsy (he/him) But look at it this way: We want D8 to be Twig 2, SF4, etc. compatible now. This is the same thing for D9. And then we make an _informed_ decision whether we go a step further and require SF5 once we know wha breaks.
xjm @Gabor Hojtsy (he/him) I also had an idea about offering "bridge" deprecations on behalf of SF (or with hteir help)
xjm To tell people things are deprecated in SF5
catch The only additional work to make Drupal 9 SF5 compatible is dealing with new Symfony 4 deprecations in the minors instead of suppressing them.
Gabor Hojtsy (he/him) I understand the approach. I think deferring that decision later will mean we are working less on some things that would make the transition easier, but we’ll only see in hindsight how this works out. I don’t have specifics just feelings.
catch So far at least.
xjm @Gabor Hojtsy (he/him) If we decide not to do it, we'll have to make the jump in 10 anyway. I can see wanting to limit risk this time around. But I want a real assessment of the risk and potential mitigations first. :slightly_smiling_face:
Gabor Hojtsy (he/him) Ack.
xjm @Gabor Hojtsy (he/him) And I think so long as we _do_ scope CKE4/5 to later, then we have room for this one and Twig, whihc are less easy to run as experimental
xjm Will report next meeting on how things go with them
mglaman Trying to keep my ear to all of this. Centarro (the artists formerly known as Commerce Guys) is continuing on building Drupal Commerce as one of the best eCommerce platforms. We obviously have our own team tied up in our own contrib, but I want to see how we can help ensure the platform transitions to D9 easily and with longevity. That’s my take
andypost Is there any links to issues sf4 vs sf5 compatibility? I recall only sessions & autoloader BC shims which we need to move to core
mikelutz The branch for SF5 isn’t open yet, and 5.0 won’t be released until November.
mikelutz The only roadmap we have to guide us is deprecation notices in Symfony 4.
mikelutz If we really want to keep the possibility of Symfony 5 in D9 open, we will need to be involved in it’s development once the branch opens, which I expect to be in May.
mikelutz If we wait until the release it will probably be too late, but if we can keep par with the changes over the next 6 months as they happen, we might have a chance, and if we are active with the Symfony devs, then we have the chance to influence SF5 development in a way that works for us.
xjm Yep, I definitely reommend at least a trackcing issue against core as soon as they open
mikelutz @alexpott and I have been trying to be more active in the symfony dev community since DrupalCon. It would be nice to have other Drupal Devs active there too. I think if they see us engaging and contributing back they will be more inclined to work with us on issues in the future.
mglaman @mikelutz you know you can always ping me something
mikelutz @mglaman
mglaman :troll: of course
catch This is the main issue tracking changes.
catch Symfony 4.3 is the next minor and could be any time in the next 4 weeks, so updating to that version is the next big step.
mikelutz Yes, and I expect they will open the 4.4 branch and the 5.0 branches at the same time.
catch is the main blocker at the moment
mikelutz And we are trying to work with symfony devs to find a solution for that upstream.
andypost
What blocking it?
Gabor Hojtsy (he/him) @catch ^^ ?
catch @mikelutz I re-opened the Drupal issue though since it doesn't look like they're keen.
andypost @mikelutz our session issue in the same state
catch @andypost either of the two sub-issues would be enough to close it
catch or
mikelutz @catch Not too keen in SF4 because of BC issues, but if we are going to target SF5, there is some opportunity to work on it.
mglaman the APCu class loader from Symfony is such a performance hit
andypost I bet single classmap entry better target instead of copying unmaintained code
catch @mikelutz I think we should commit something for Symfony 4, we can re-open for Symfony 5 too of course.
mikelutz @catch I have no objection, it would be nice to be able to have a testable symfony 4 patch working that we could monitor against symfony changes.
xjm @larowlan Above thread ^ is relevant for SF 4 vs. 5 as per our chat
xjm @mikelutz If you wanted to keep an eye on SF5, that would be very welcome

@sushyl has joined the channel

4️⃣ Related to the above what do people think about a PHP 7.3 requirement for Drupal 9?

mglaman Yes. If anything the min has to be 7.2
mglaman The faster we decide the faster hosting platforms will comply
johndevman Yes!
xjm Yes, this will definitely be the min.
catch Yep 7.2 is the absolute minimum, 7.3 might be required by dependencies by the time we want to release.
Nick Wilde :heavy_plus_sign: :thumbsup_all:
larowlan Also sf5 may force our hand

5️⃣ Drupal 9 readiness docs. Where are they, where is more help useful?

xjm @bnjmnm ^
xjm @bnjmnm Sorry I pinged you earlier but missed the "not in channel" :slightly_smiling_face: welcome
xjm @Gabor Hojtsy (he/him) Do you know who has been the lead so far? You and Angie? Or is someone else working on end user docs?
Gabor Hojtsy (he/him) our main docs page is
Gabor Hojtsy (he/him) we want to break this down to multiple pages carefully and redirect the fragments properly (that will be fun)
Gabor Hojtsy (he/him) but we should move a lot of the offsite docs here
Gabor Hojtsy (he/him) eg. should be in the docs
Gabor Hojtsy (he/him) @webchick and I have been working on this so far yeah
Gabor Hojtsy (he/him) we also have wireframes for a D9 landing page on
xjm @Gabor Hojtsy (he/him) I made my own version for at least the 8.9/9.0 part over the weekend for the release cyle overview
Gabor Hojtsy (he/him) that would tell people the key facts and lead to FAQ, etc.
Gabor Hojtsy (he/him) I also created an open source “State of Drupal 9” slideshow that @chr.fritsch presented over the weekend in Munich :slightly_smiling_face:
Gabor Hojtsy (he/him) I’ll post a blog post about this possibly tomorrow and encourage people to present it
Gabor Hojtsy (he/him)
Gabor Hojtsy (he/him) I’ll present this in Minsk in 2.5 weeks and some variant of it at DevDays in June
Gabor Hojtsy (he/him) Eeveryone should do their mini “tech Driesnotes” at local camps and meetups and companies :slightly_smiling_face:
Gabor Hojtsy (he/him) @bnjmnm anything specific you are interested to help with?
bnjmnm At minimum, I'd like to be involved editing/reviewing the new docs and making sure there's Acquia time set aside for me to do that.
Gabor Hojtsy (he/him) :thumbsup:
Gabor Hojtsy (he/him) is the D9 landing page @webchick and I drew up
Gabor Hojtsy (he/him) I am trying to negotiate that with the DA to make sure it fits their plans
Gabor Hojtsy (he/him) then this would be the door to Drupal 9, hopefully top search result, etc.
Gabor Hojtsy (he/him) the existing needs to be broken down to more pages and a lot more details added
webchick @Gabor Hojtsy (he/him) are we thinking this is the main landing page @ /documentation/9 ?
Gabor Hojtsy (he/him) I think it will likely be :slightly_smiling_face:
Gabor Hojtsy (he/him) or somesuch
Gabor Hojtsy (he/him) but it could be /documentation/9
Gabor Hojtsy (he/him) I think the structure of this page does not fit well with docs
Gabor Hojtsy (he/him) so it would be /9 more likely
webchick Ah, that’s even better. :slightly_smiling_face: Short URLs ftw!
bnjmnm Is there a doc yet that attempts to list what should be covered within ?
webchick Basically, that horrible google drawing @Gabor Hojtsy (he/him) shared above… (I can say that because I “drew” it ;))
webchick The intent tho is to make it in a style like
Gabor Hojtsy (he/him) @bnjmnm yeah we hope to provide a high level value list, lead to FAQs, timeline, show progress on how it goes, etc. mostly a very high level “Driesnote” info, then lead to a D7 migrations landing page (that we also drew up)

6️⃣ Dependencies we’d like to consider removing. Starting with jQuery UI.

Gabor Hojtsy (he/him) Any other dependencies that look realistic to be removed?
catch is very doable.
Gabor Hojtsy (he/him) yay!
xjm Oops missed this earlier. Also what about Diactoros?
xjm We have at least 2 PSR-7 implementations and we could go to a different PSR-17 implementation instead of just updating Diactoros in
xjm

@bnjmnm has joined the channel

7️⃣ Next steps on the fixes to the coder rules for deprecations and the core test issues so we can continue to work toward finalizing that.

Gabor Hojtsy (he/him) So we did
Gabor Hojtsy (he/him) then we found out some inconsistencies
Gabor Hojtsy (he/him) after the coder rules were implemented
xjm So there are two issues I'm aware of:
xjm 1. The "removed by" is missing from the trigger error rule (I think)
xjm 2. Some conrtib don't want to require a CR. I think we should keep this requirement though. If htey want hey ccan make a single page documenting their deprecation info and link it everywhere. And ccustom code could mamybe ignore the rule?
Gabor Hojtsy (he/him) @xjm trigger error may be used in various code paths that do not mean something removed
xjm One of the steps for me to getting the rule adopted as the standard is making sure it does the right things to core. :slightly_smiling_face: So
xjm @Gabor Hojtsy (he/him) So it may be we need to chcange the rule
Gabor Hojtsy (he/him) which is why it does not have the removed by as standard, BUT I think suggesting and ideally enforcing the same words where it DOES mean remove is key
xjm Like trigger_error() is a legit function to use; I didn't realize it was hitting everything?
Gabor Hojtsy (he/him) @xjm hm, where would this say removed?

`@trigger_error('Using EntityTranslationRenderTrait without implementing a getEntityRepository() method is deprecated in drupal:8.7.0. EntityTranslationRenderTrait::getEntityRepository() will be made abstract in drupal:9.0.0. Implement ::getEntityRepository() on the class. See ', E_USER_DEPRECATED);`
xjm It should only matcch the trigger_error about a deprecaction
xjm @Gabor Hojtsy (he/him) But why would that rule be different between the @deprecacted and the @trigger_error()?
xjm It seems aside from the point.
xjm And what's more is the trigger_error were _failing_ when they had the normal/ccorrect form with a removal
Gabor Hojtsy (he/him) yeah I agree when there is a @deprecated, THEN the trigger_error() should be the same text
Gabor Hojtsy (he/him) the coder rule is written to check trigger_error()’s to follow rules when they trigger a E_USER_DEPRECATED
xjm I also think any @trigger_error() for a deprecated param or w/e needs the target version
Gabor Hojtsy (he/him) `will be made abstract in drupal:9.0.0`
Gabor Hojtsy (he/him) it has :slightly_smiling_face:
xjm "Will be made abstract in 9.0.0" is just another way of saying "Direcct extensibiliy weill be removed in 9.0.0".
xjm It's not a reason for the trigger_error() rule to disallow the version req entirely
xjm The important thing is that there's a project and version at hte end
Gabor Hojtsy (he/him) yeah I am not a good rubber duck for arguing about correct English, so I stepped back from arguing about that when actual English speakers got involved :slightly_smiling_face:
Gabor Hojtsy (he/him) I am not sure the people from the issue are here, so it would be useful to get all that feedback on the issue.
xjm I unfortunately anc't partiipate in the main issue, but these problems acme up when they started hte core conversions.
xjm Unfortunately I acn't be involved in the issue.
xjm But this seems like a simple bug in the implementation that coculd use its own issue.
Gabor Hojtsy (he/him) My feeling is we are going around in circles so I don’t consider myself the right person to lead fixing this.
Gabor Hojtsy (he/him) @mglaman @hotwebmatter @Alona Oneill this is an area that could apparently use someone if you have colleagues looking for something to clean up ^^ :slightly_smiling_face:
Alona Oneill Okay. Thanks!
xjm My suggestion is to file new bug reports about the rules as cchild issues of the original issue where they were implemented.
xjm Would also be good to discuss what should be done for the case where hte person didn't want a CR for their custom ccode and wjhat our offiial recommendation is in that case.
Gabor Hojtsy (he/him) IMHO the first step would be to write down exactly what rules should be followed by the code, then decide if the technical working group should announce / wait for comments / approve that again
xjm Well, I thought we'd already done that, and IMO the rules don't cocrrespond to what's documented in the IS of the issue that was supposed ly approved
xjm That or the IS was inconsistent or inomplete or something.
Gabor Hojtsy (he/him) the IS is @trigger_error() format
`%thing% is deprecated in NaNn-version%. %extra-info%. See %cr-link%`
Gabor Hojtsy (he/him) which is the approved format
Gabor Hojtsy (he/him) we can implement something else but then what is the point of the approval process?
xjm I dunno, I read the IS and not the comments and thought it was fine, but did not realize htere was htis incconsistenccy.
xjm Part of the approval process is seeing how it would disrupt core
xjm That's the step we're on
xjm And we're doing it and finding the ccurrent implementation is massively disruptive.
xjm So this is exactly the point of the proecss, really.
Gabor Hojtsy (he/him) Right, so which is why I am saying we need to go back and suggest a better format and no point in implementing it, but I don’t understand the better format based on different people saying different things and neither on the issue, so I feel powerless to do anything about this. I went on to other things where I can make progress.
xjm I really think it's just an implementation problemm
xjm But if someone else ccould take the lead that'd be great; I just cannot interacct myself on the main policcy issue

8️⃣ Updates on deprecation checking tools: drupal-check, phpstan and Upgrade Status.

mglaman :slightly_smiling_face: thanks
mglaman Deprecation messages: I need to fix a failing test on this PR and play diplomacy with another core contributor:
mglaman I’ve added CircleCI for workflows and more in depth integration testing w/ Drupal Check. Reproducing some weird failures and need to investigate
mglaman I added CircleCI to phpstan-drupal which let me catch a bug for autoloading of `Drupal\Tests\*` files
mglaman I’ve made it easier to add test cases for reported bugs. Uncovered a possible quirk here or there. Fixed one.
Gabor Hojtsy (he/him) wow nice progress @mglaman
mglaman ondrejmirtes has asked if I was interested in becoming a core contributor to phpstan and passed on a list of things and some information. so there is also that
Gabor Hojtsy (he/him) I had some discussions with @herczogzoltan as to how we can make Upgrade Status follow drupal-check improvements closer (same holds for phpstan on drupalci)
Gabor Hojtsy (he/him) neither directly uses drupal-check so if the fixes are not in the dependencies, then those don’t get them
mglaman I try to fix as much in phpstan-drupal as possible. The only “fixes” that should need to go into Drupal Check is.. whatever is passed to the CommandHelper::begin
mglaman if I notice anything I’ll pass the info along
Gabor Hojtsy (he/him) thanks
andypost @mglaman are you going to add php-version compatibility analysis to drupal-check, like hunt php 7.4
Gabor Hojtsy (he/him) @herczogzoltan released alpha2 of Upgrade Status which has some improvements as well
Gabor Hojtsy (he/him) chunks parsing to 30 files per projects so it can parse big projects without timeout/memory problems
Gabor Hojtsy (he/him) also catches fatal PHP errors in parsing and stores them
Gabor Hojtsy (he/him) UI completeness and tests are up next in the list to work on
mglaman @andypost it could; I wasn’t thinking that far yet
Gabor Hojtsy (he/him) would be useful to get more testers
Gabor Hojtsy (he/him) I posted to encourage that

9️⃣ Automated deprecation fixing!

Gabor Hojtsy (he/him) was posted last week :slightly_smiling_face: it looks nice! did someone try it out?
Gabor Hojtsy (he/him) @mxr576 built it
mglaman Should we try to roll another runner in `drupal-check` that executes Rector?
Gabor Hojtsy (he/him) why not :slightly_smiling_face:
Gabor Hojtsy (he/him) either way I think it needs to be made super-clear that the fixes suggested need heavy human review
mxr576 Human review and automated tests :-)
mxr576 That is the best combination

@cweagans has joined the channel

🔟 Thanks all for coming, this is it for the meeting, keep up the great work! :blue_heart:

xjm Thanks @Gabor Hojtsy (he/him)!
Gabor Hojtsy (he/him) :bow:
mglaman thank you @Gabor Hojtsy (he/him)!

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
commented
Issue summary: View changes
xjm’s picture

xjm
she/her
Primary language English
commented

I'd like to give an update on major dependency upgrades (Symfony, CKEditor, Twig). catch and I had a discussion about all this last week.

Also, one of our teammates has an interest in improving documentation, so maybe an update of where D9 readiness docs are at?

xjm’s picture

xjm
she/her
Primary language English
commented

And possibly, next steps on the fixes to the coder rules and the core test issues so we can continue to work toward finalizing that.

xjm’s picture

xjm
she/her
Primary language English
commented

Another topic: Dependencies we'd like to consider removing, starting with jQuery UI https://www.drupal.org/project/drupal/issues/3051352

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Issue summary: View changes
pandaski’s picture

pandaski commented

topic suggest: A better way of handling the countries

The country list is kept up-to-date with CLDR data via core/scripts/update-countries.sh.

That data is maintained by Unicode and this approach does cause some delays between the name approvals and the data changing

alonaoneill’s picture

alonaoneill commented

Gábor Hojtsy credited NickWilde.

Gábor Hojtsy credited andypost.

Gábor Hojtsy credited bnjmnm.

Gábor Hojtsy credited catch.

Gábor Hojtsy credited hotwebmatter.

Gábor Hojtsy credited johndevman.

Gábor Hojtsy credited larowlan.

Gábor Hojtsy credited mglaman.

Gábor Hojtsy credited mikelutz.

Gábor Hojtsy credited mxr576.

Gábor Hojtsy credited shaal.

Gábor Hojtsy credited webchick.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Issue summary: View changes
Status: Active » Fixed

Meeting log posted. Special thanks to @mlhess for the data source.

Gábor Hojtsy credited mlhess.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Separately crediting @mlhess because "Crediting others cannot be longer than 128 characters".

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

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.