2020 WordPress Release Squads

Update, June 6 – Changed to include the newest member of the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. squad, Mary Baum, on Marketing. -Josepha

Excellent progress has been made on WordPress 5.5 so far, and I’m here to do some updates! One of the big things missing from that post was some clarity around who was joining the release squad to help makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure this is a success. This post has the names we know, and I’m happy to take corrections or suggestions as well. 🙂

  • Release leadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg @matt
  • Release coordinator: Jake Spurlock @whyisjake
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: David Baumwald @davidbaumwald
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: Sergey Biryukov @sergeybiryukov
  • Editor Tech: Ella van Durpe @ellatrix
  • Editor Design: Michael Arestad @michael-arestad
  • Media Tech: Andrew Ozz @azaozz
  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Tech: JB Audras @audrasjb
  • Docs coordinator: Justin Ahinon @justinahinon
  • Marketing/Release Comms: TBD @marybaum

Joining simultaneously is the WordPress 5.6 release squad! I’ve tagged all of them here, but have left out role assignments. If they make it part way through the ride along process of WP5.5 and decide it’s not what they signed up for after all, then they can step back and someone else can join. 🙂 The WP5.6 release squad will be announced in a roundup/kickoff post of their own.

@afshanadiya @alliennimmons @amandahdm @amykamala @anchenlr @angelasjin @anyssa @annezazu @aurooba @Azhiyadev @bethannon1 @bethsoderberg @breannmcdede @cguntur @chanthaboune @daydah @elmastudio @eringoblog @estelaris @francina @helen @hellofromTonya @isabel_brison @jainnidhi @katiejrichards @laurora @luminuu @m_butcher @marybaum @mbguery @meaganhanes @meher @mekalekahi @melchoyce @metalandcoffee @michelleames @monikarao @newyorkerlaura @planningwrite @poena @rebasaurus @sarahricker @shital-patel @sncoker @thelmachido @thewebprincess @tray @trisha_cornelius @whitneyyadrich @yvettesonneveld

#5-5 #5-6 #planning

Devchat meeting summary – April 22, 2020

The chat was led by @davidbaumwald based on this agenda.

The full meeting transcript is available on Slack.

Highlighted blogblog (versus network, site) posts

@davidbaumwald shared some posts from the Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog.

5.4 Retrospective – Call for feedback: the deadline is April 30 and everyone is welcome to leave a feedback.

Proposal: Core Team Rep Elections: the deadline for nominations and self-nominations is May 4.

We’re applying to Season of Docs: a new working group that needs help!

WordPress 5.5: Call for Tickets: the deadline is April 30.

Upcoming Releases

WordPress 5.4.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 was supposed to be released yesterday Wednesday, but there were some miscommunication between Core team and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ team. The RC has then been pushed back to this Friday. The Gutenberg changes that are going to be included in the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. are listed in this pull request. The milestone for this point release is also cleared.

@davidbaumwald reminded that for 5.5, all the maintainers have been pinged about potential features and focuses.  If you’re a component maintainer and haven’t replied yet, please do, so scope and schedule can be proposed.

He also said that work for 5.6 release, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and @francina will work on phase 2: identifying missing roles and cohorts to organize the team that will ride along with 5.5.

Components Check-in

@francina has pinged #meta team about having a weekly scheduled post to check Components status; @dd32 expressed some concerns about the noise that it will create. @davidbaumwald suggested to move on with this for a three-month test.

@audrasjb gave an update about plugins and themes auto-update feature. The team released version 0.6.0 of the Feature Plugin yesterday Wednesday.

The Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. contains all the identified must-have features and the UIUI User interface was reviewed by several teams. The team is now about to write the Core merge proposal post on Make/Core. More infos here.

Open Floor

@apedog asked a question about routing in WordPress Core. He stated that the WP class having $_SERVER hard-coded into it. And this would require re-writing the methods inside WP class, but without changing its functionality.

@clorith said that he’s generally against the bot idea for a general channel with lots of chatter, and the loss of potential input to backscroll. If it’s going to happen, it should be on Make/* somewhere for consistency and visibility.

@audrasjb pointed out to #16557, a long standing ticketticket Created for both bug reports and feature development on the bug tracker. raised by some people in the French WordPress community. It appears it would be a great SEO enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to provide proper filters on redirect_guess_404_permalink() function.

He milestoned the ticket to 5.5.0 and refreshed the existing patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. after testing it. This still needs some unit tests, but before writing them, it would be nice to get a quick review on the current proposal.

@netpassprodsr called for review on #49832.

#5-4-1, #5-5, #5-6, #summary

Dev Chat Agenda for April 22, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, April 22, 2020, at 20:00 UTC.

Announcements

If anyone has any announcement to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)., now is the time!

Upcoming Releases

  • Work has started on WordPress 5.4.1 lead by @whyisjake
  • All the maintainers have been pinged about 5.5. Some replied, some didn’t – please do, so scope and schedule can be proposed.
  • Work for 5.6, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and I will work on phase 2: identifying missing roles and cohorts to organise the team that will ride along with 5.5

Highlighted blogblog (versus network, site) posts

Components Check-in

I have pinged MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. about having a weekly scheduled post to check Components status – @dd32 expressed some concerns about the noise that it will create. I would still suggest to move on with this for a three-month test.

But in the meantime… the usual:

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

Open Floor

Got something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-4-1, #5-5, #5-6, #agenda, #devchat

Dev Chat summary – March 25, 2020

@francina facilitated the chat on this agenda.

Full meeting transcript on Slack

This devchat marked week 11 of the 5.4 release cycle.

Announcements

WordPress 5.4 Release Candidate 4 was released on Tuesday March 24, 2020 and everything went smoothly.

@audrasjb shared an update on WP Auto-updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.: it was moved from his personal GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ account to WordPress/wp-autoupdates which is the new official GitHub repository of this project. The #core-auto-updates team will try to ship version 0.4 before WP 5.4 is released. This new version aims to handle auto-updates for themes.

@afragen asked for a review of some Trac tickets which are all associated with Theme compatibility checks and will likely have interaction with the auto-updates feature. The idea is to ship them early in WordPress 5.5.

@whyisjake pointed out that he really like the work that is going on in #core-auto-updates SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and think that trying to land in the next few releases would be excellent. Related, He’d love to see #core-passwords (two-factors authentification – 2FA) land in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. too. In his opinion, the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is so mature at this point that having it left out almost seems like an omission. @whyisjake is going to work on a merge proposal.

@clorith raised that it would be necessary to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure that the 2FA proposal also highlights the concerns with how to address users locking them selves out (which was the major holdback previously).

@azaozz announced that the patch for image lazy-loading attribute is ready for testing.

Upcoming Releases

The current major is 5.4, scheduled to go out on March 31st 2020; please keep testing for all the bugs!

There are two ways do it:

Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. has been branched to 5.5 on the beginning of March. That means 5.5 is officially in Alpha.

@francina announced that work for 5.6 –which is going to be an all-women release– has kicked off with an initial round of messages going out to the women that expressed interest. @angelasjin @francina and Chloé Bringmann are contacting them to hear if they are still interested, what skills they have and what expectations.

Components Check-in

@francina shared a proposal to change the Components Check-in. This is always done towards the end of the chat and feels rushed. There is never really time to dig into the topics they might bring up. Francesca shared two ideas:

  1. Schedule a weekly post where they can leave their status update, like the one for Community deputies.
  2. Adopt a Slack Bot that once a week will ask the maintainers for a status update: maybe in a new component-maintainers Slack channel. Core is getting very busy with TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and Travis bots, and RSS.

@johnbillion added that trying a weekly post could be a good idea. Maybe every Tuesday so it’s ready for the dev chat on Wednesdays in case anything comes up.

@francina proposed to talk to #meta to set this up and test drive it for 8 weeks.

Open floor

@isabel_brison proposed to create a set of guidelines for Internet Explorer support. The CSSCSS Cascading Style Sheets. team kind of decided on starting to deprecate it, and “graceful degradation” seems a good way to go forward, meaning Core can use unsupported technology to make non-essential enhancements. Isabel wants to agree on what’s “essential” here, and created a Trac ticketticket Created for both bug reports and feature development on the bug tracker. to start the discussion: #49696

@paaljoachim suggested to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) default full screen mode to 5.5 as there is a pull request on Gutenberg project GitHub repository to provide an alternative approach.

@audrasjb pointed out that the proposal in this pull request would be a way better than the current implementation.

@whyisjake added that this is not a realistic change for WP 5.4, it’s a proof of concept, and not a fully tested feature.

@francina confirmed that @matt took the decision to ship WordPress 5.4 with this feature. Matt also commented in the Accessibility Team statement post.

@joyously stated it’s hard to contribute when concerns are ignored. @chanthaboune answered she can understand how they can feel ignored. A lot of that research gets done solo, and it’s often hard to remember to recap your own research. For full site editing to be a reality by the end of the year, the work can start bringing incremental changes. This change is feeling very jarring, but there is more worry about not have any mid-point between here and Full Site Editing.

@peterwilsoncc, @clorith and @audrasjb agreed that since RC4 was released, it’s not realistic to revert this change. The discussion can continue in a post-mortem post on Make/Core.

#5-4, #5-5, #5-6, #dev-chat, #feature-autoupdates, #feature-lazyloading, #two-factor

All-women Release Squad

I recently commented on Twitter that I have a stretch goal of having a releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. squad that is all women by the end of 2020. With the work I’ve been doing to prepare for my upcoming sabbatical, I’ve been giving a lot of thought about how to do this and what I hope it accomplishes.

What’s the Goal?

The primary goal of any release cycle is to ship a stable and enhanced version of the WordPress CMS, but for the past year or so we’ve also been sharing the procedural work with a team of people. I affectionately refer to them as the release squad.

My hope is that with a release squad comprised entirely of people who identify as women, we’ll be able to increase the number women who have that experience and (hopefully) become returning contributors to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and elsewhere. This doesn’t mean the release will only contain contributions from women. And if our current squad training process is any indication, it also doesn’t mean that we’re asking a squad to show up and do this without support.

What’s the Plan?

I have a list of about 75 women who raised their hands to participate in this release squad. I think that we can use the current squad training process (ride along, navigate while someone drives, drive while someone navigates) to progressively level up everyone’s skills. Stepping away at any time is an option as long as it’s communicated. 🙂

So far, this is the broad idea for how we will get there:

  1. Prepare and Plan
    1. Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure the timing works for anyone who already volunteered.
    2. Determine current skills and team involvement.
    3. Reach out proactively to gather additional people where I don’t have quite enough.
    4. Gather groups and group mentors.
  2. Ride Along on Release 5.5
    1. Join triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions, meetings, etc and ask every question.
  3. Navigate Release 5.5.x
    1. Collaborate with the 5.5 release squad to navigate a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. and ask every question.
  4. Drive Release 5.6
    1. Drive the release while collaborating with some long-time women contributors.

How Can You Help?

The preparation for this will be a big undertaking, but probably just as much training effort as any other release squad I’ve worked with. It’s still a stretch goal, but I figure the best way to get there is to get started. I’m interested to hear from:

  • Anyone who wants to be a mentor or part of the release process.
  • Anyone who has a little extra time to help me with the preparation.
  • Anyone who has questions about how this will work. 🙂

#5-6 #planning