Talking Drupal #448 - D11 Readiness & PHPStan

Today we are talking about Drupal 11 Readiness, What you need to think about, and PHPStan with guest Matt Glaman. We’ll also cover MRN as our module of the week.

For show notes visit: [www.talkingDrupal.com/448https://www.talkingDrupal.com/448)

Topics

• What do we mean by Drupal 11 Readiness
• How will this be different than 9 and 10
• Top 5 tips
• D11 Meeting and slack channel
• Will this be easier
• Major issues
• What is PHPStan
• How does it play a role
• How is PHPStan Drupal different than PHPStan
• Does using PHPStan with drupal reduce the need for tests
• How do you see it evolving over the next few years
• Drupal 12 wishlist

Resources

• PHPStan Drupal
• PHPStan
• Herodevs DrupalCon Party
• Smart date BC calls
• Contrib semantic versioning thoughts
• Change records
  • Drop is always moving
• Project analysis
• Gabor article Drupal rector
• Project update working group
• LTS even odd
• PHP version
• PHP stan rule levels
• Title issue

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Matt Glaman - mglaman.dev mglaman

MOTW Correspondent

Martin Anderson-Clutz - mandclu

• Brief description:
  • Have you ever wanted an easy way to generate detailed release notes for your contrib projects? There’s a web app for that
• Module name/project name:
  • MRN which is short for Maintainer / Module Release Notes
• Brief history
  • How old: created in Aug 2022 by today’s guest Matt Glaman
• Maintainership
  • Actively maintained, latest updates were earlier this year
  • Code project at https://github.com/mglaman/drupal-mrn has 13 open issues
• Usage stats:
  • Currently no usage reporting, but a tool I’ve been using a ton lately as I get modules ready for Drupal 11
• Module features and usage
  • It’s very simple to use, you just enter the machine name of your project, and then the numbers of the releases you want it to compare
  • It will generate the structure for your release note, include a spot for you to write a summary at the top, a list of contributors that links to their profiles, and a list of issues
  • Previously part of Matt’s drupalorg CLI project, MRN is now a lambda function on AWS, so there’s nothing to download or install
  • I like that you can choose which tags you want to compare, so if the release is part of a branch that doesn’t yet have a stable release, I’ll put a comparison to the previous release in the branch at the top, and then a comparison to the current stable release below it, so people can see the full list of everything new they’ll get by moving from the stable release
  • It’s worth noting that because this works from the git history, you need to make sure you credit everyone properly before clicking to merge an MR in the Drupal.org UI. You can give credit to other people after the fact using the checkbox and they’ll get contribution credits, but won’t be included in the release notes generated by MRN