Discussion: Training’s contribution to the 6.5 release (and beyond)

The WordPress 6.5 release squad has been announced. This next release is scheduled for March 26 and now’s a great time for the Training Team to discuss how we’d like to be involved.

Below is my proposal to kick off the discussion. Let’s discuss this in the comments below until February 5th. Team reps will then summarize the discussion by the team meeting that week.

Prioritize Learning Pathways content

The Learning Pathways project is a priority for the Training Team this year, with a scheduled launch for July 2024. Considering the limited number of content creators we have on the team right now, we do not have enough resources to meet that deadline and create a lot of release-related content at the same time.

Proposal around priorities

• Continue to prioritize developing Learning Pathways content.
• Identify no more than 3-5 pieces of high-impact content related to the release and clearly list these in the team.
• Find opportunities to onboard additional content creators who can assist with this content development work.

Modifying GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ triaging processes

Historically, Training’s focus during releases has included identifying content needing updates as a result of the release. This has been done by reopening GitHub issues and, if the original assignee is unresponsive, re-assigning issues to new assignees.

As the team has started to track and analyze GitHub data (see Training Team 2023 Year In Review), we’re finding this process of reopening issues and changing assignees skews important metrics that represent team health – such as the “time to close” on an issue. To ensure the team can track and report accurate metrics, I propose the following changes.

Proposal around changes to GitHub triage processes

• We should no longer re-open closed GitHub issues to report content needing updates.
• Instead, if content needs notable updates, each update should be submitted as a new issue, using the Feedback issue template.
• Faculty Editors are encouraged to actively check the Learn Content – Feedback GitHub project board and validate/apply feedback submitted around the time of the release.

Once again, let’s discuss this in the comments below until February 5th.

#procedures