The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in our bug tracker.
@adamsilverstein gave a great update on the progress of the focus. First, all issues and ideas related to focus will be tracked in this GitHub project. This will facilitate asynchronous contributions and discussions. The top priority issue on the project is this one, for creating a WebP module, and port the code to the repository.
On top of that, the focus meeting last Thursday was a success and the team is planning to hold a next one. Keep an eye on the Make/CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.blogblog(versus network, site) and the #core-media channel on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. to keep up with the agenda.
There were also several discussions about the main projects of the focus: WebP by default in WordPress Core and the migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of existing images into the WebP format. Here are the links to the discussion pieces on Slack:
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.
Since most of the people in this focus are deeply involved in the next release, there are no major updates at the moment.
Measurement
For this focus, there were some discussions about starting a dedicated side conversation (see thread). Currently, the team is still thinking about the best form for this conversation, chat or video call. If you have any opinions, feel free to leave a comment in the thread linked above or on this post.
Performance features development coordination
There is currently this issue on the GitHubGitHubGitHub 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/ repository regarding the code infrastructure of the performance modules. This step is very important to move forward, so feel free to leave a comment or feedback on the issue.
Open Floor
Jérôme Vieilledent (@lolautruche on Slack) mentioned before the meeting that Blackfire and Platform.sh are willing to support the WordPress Performance team initiative. Blackfire might be interested in donating an account to the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ organization for the team’s purposes. See Slack discussion here.
As a community, we need unified documentation on setting up a WordPress development environment. The current problem is that we have several different ways and locations documented, so depending on how a developer may start in WordPress may differ greatly from others.
The ideal scenario is one set of quality documentation that all the handbooks can point to help guide someone new to the project in setting up a development environment.
A few new wrinkles as this is not just a documentation issue.
There has been a fair amount of effort going towards making wp-env that standard. The benefit is wp-env allows for a small set of commands to get started. A developer doesn’t need to setup web servers, PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher, or databases, it is all handled by containers. In this case, Docker.
Unfortunately with recent news, Docker Desktop is no longer free. The Docker engine itself is open-source and one of the main reasons it has grown in popularity. However, the Docker Desktop is not, and it is the primary (and easiest) way to install a Docker VM on Windows/Mac. Linux doesn’t require a VM to run Docker, can’t we all just switch to Linux? 😉
The services agreement for Docker Desktop:
4.2 Specific License Limitations – Docker Desktop.
(a) The Docker Desktop component of the Service at the level of the Personal Offering (as described on the Pricing Page) is further restricted to: (i) your “Personal Use”, (ii) your “Educational Use”, (iii) your use for a non-commercial open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, and (iv) your use in a “Small Business Environment”.
(b) For purposes of this Section 4.2: (i) “Personal Use” is the use by an individual developer for personal use to develop free or paid applications, (ii) “Educational Use” is the use by members of an educational organization in a classroom learning environment for academic or research purposes or contribution to an open source project and (iii) a “Small Business Environment” is a commercial undertaking with fewer than 250 employees and less than US $10,000,000 (or equivalent local currency) in annual revenue.
The Section (a) restrictions above reads that Docker Desktop is allowed for personal and open-source use, but not if you work for a company with more than 250 employees or more than $10m revenue.
These restrictions are not in-line with the WordPress community and the open source ethos we want to promote. This makes it difficult to suggest Docker as the primary tool for setting up a development environment.
Which leads us to this post and discussion. What development environment should we recommend for new WordPress developers?
The main criteria I see for a tool are:
open-source
ease of use to setup and run
cross-platform (Windows, Mac, Linux)
If there is no good solution, do we consider creating our own? Or reviving a previous attempt at creating a simple development environment?
These are some initial thoughts to get the discussion started, what do y’all think?
A revised release schedule for WordPress 5.9 is available, with the final release planned for 25 January 2022.
Why the delay?
Near the end of the original alpha release cycle, issues arose that related to multiple major features planned for the 5.9 release, including:
Full Site Editing (FSE), which is a collection of features, such as global styles interface, Navigation BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., block themes, template editors, and site editing flows.
The Twenty Twenty-Two (TT2) theme, which depends on these FSE features.
The 6.0 release isn’t due until April 2022—too long for the community to wait for them. After processing this list of issues, CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team saw the features could ship in 5.9 with the revised schedule.
This decision, to delay the 5.9 release, was not made lightly. The following section shares the decision-making process.
The decision-making process
Careful, thoughtful, open discussions happened in the release squad channel, that considered options and impacts:
Move the specific pieces needing fixing to 6.0.
Move the fixes to a 5.9 minor releaseMinor ReleaseA 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..
Move the fixes to 6.0.
Move these major features to 6.0.
Delay 5.9 to include fixes.
As the FSE features are very closely intertwined, removing some of its pieces would risk making the release unstable. To avoid delivering a sub-optimal experience, moving fixes to a 5.9 minor or 6.0 was ruled out.
It came down to a choice between:
Option 1: Remove these major features from 5.9 to target shipping in 6.0 in April 2022.
Option 2: Delay the release to ship the promised major features in 5.9 in January 2022.
After consulting with advisors from previous release squads and the Core Editor team, based on the current information available, the release squad determined shipping these major features sooner rather than later would have more benefits and less impact.
The release squad respects that the community has expectations and plans for these features. The extra time in the new schedule will help everyone involved deliver the 5.9 features the community has been waiting for.
Seasonal considerations
The BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and RC release cycles have two jobs: to get the community involved in testing and delivering feedback, and to give contributors a block of time to fix identified issues before the final release.
The third major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of the year was originally scheduled for the middle of December. Historically, fewer people are available the last two weeks of a year and the first week of a new year, because of various holidays, time off, and end-of-year and annual planning. This means there would be fewer people to test, give feedback, fix reported issues, and help package each release.
The revised schedule takes into account the realities of year-end and offers an optional Beta 4 if needed.
A schedule that delivers the full release
5.9 is still in feature freeze. Work from here on is strictly to address the changes that get the release to a stable state.
The revised schedule also has a number of built-in safety measures:
More transparency. Constant communication between the release squad and Core Editor team throughout each week, so everyone involved knows the status of relevant items and can surface (and meet!) needs as early as possible.
🔺blockers merged by Beta 1. An agreement that blockers (identified as🔺 in the list) must be ready by Beta 1 or risk getting moved to 6.0. (Update: these items were merged last week and are no longer blockers.)
Get involved in the FSE Program testing calls including testing the site-editing experience. You can find a record of all the FSE Outreach exercises; feel free to go back and test any that interest you, but keep in mind that features have evolved.
Important: Try to break things to find things that may not work for your test sites.
If you’re available, come to the Beta and Release Candidaterelease candidateOne 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). (RC) release parties, and bring friends! Test the packages when they drop. The parties take place in the Core channel of the Make WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Come to the Slack meetings for Core and the Core Editor, and keep reading the posts on the Make.WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/blogblog(versus network, site).
Share feedback! The teams need to know everything that breaks, and everything that works really well, too.
For issues with GutenbergGutenbergThe 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/, create an issue on GitHubGitHubGitHub 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/.
For issues anywhere else, start a ticket on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
This post was authored by @opr18 (Thomas Roberts).
During a recent WordPress #core-js meeting there was a discussion about updating the JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. coding standard. The specific update that is being proposed is to change the rules relating to comments.
Currently, the standard reads:
Comments come before the code to which they refer, and should always be preceded by a blank line. Capitalize the first letter of the comment, and include a period at the end when writing full sentences. There must be a single space between the comment token (//) and the comment text.
The proposal is that the new wording should be:
Comments come before the code to which they refer, and should always be preceded by a blank line. Unless writing a linter override, or a `@see` type comment, capitalize the first letter of the comment, and include a period at the end. There must be a single space between the comment token (//) and the comment text.
The problem with the current guideline is that it is not enforceable by automated tools. It is hard for linting tools to easily distinguish between what is and isn’t a full sentence in the context of code comments.
Code reviews can quickly fill up with noisy comments and suggestions to capitalise or add periods to code comments. If this were fixable with a linting rule then these comments wouldn’t be necessary.
There are instances where it may not make sense to write in sentence case, for example: adding linter overrides or writing `see` comments where the comment may just be the name of a method or file, etc. so we would not enforce the rule on these types of comments.
If this guideline were to be amended, there would be several instances of code in the GutenbergGutenbergThe 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/ repository alone that do not follow it. It would be necessary to create a PR that fixes all of these issues. Because the change only relates to comments, a single PR can be made addressing all instances of comments that don’t follow the guideline, because the rule relates to comments only, this would have no impact on functionality so minimal testing would be required.
WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. currently uses JSHint for linting JavaScript files, and it does not appear that even the existing style guideline is enforced. Even so, if efforts were made to move to ESLint in WordPress core, implementing a fix for any comments that do not follow the standard should be straightforward.
Initially the rule could be enforced as a “warning” while the PR to fix the issues is completed and after it has been merged the rule could graduate to an “error”.
Here is a draft PR demonstrating the punctuation aspect of the proposed change: https://github.com/WordPress/gutenberg/pull/34964
As a part of next steps, this post is looking for feedback on:
How do you feel about the proposed changes to the wording of the standard?
Are there any concerns about the plan for implementing this change?
This proposal is open for feedback until October 5th, 2021 at which point a final decision will be made during #core-js office hours that day.
@audrasjb will continue in this role until another team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. is found.
@jeffpaul asked if there are any 5.9 blockers that are in specific need of help and asked what type of help they need (engineering, design, testing, etc).
The release squad is keeping a daily close eye on progress, needs, and any blockers that might surface. Discussions and updates are centralized in the #5-9-release-leads channel on Slack.
Dependabot scanning is now configured for GitHubGitHubGitHub 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/ Actions. This eliminates the need to manually check all GitHub Actions used within workflow files for updates. See ticketticketCreated for both bug reports and feature development on the bug tracker.#54503 for more details.
NodeJS is pinned to the 14.x version in the .nvmrc file to ensure contributors are able to contribute without issue until compatibility with version 16.x can be confirmed in both trunktrunkA 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. and the GutenbergGutenbergThe 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/ repository on GitHub. See ticket #54502 for more details.
Some PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warnings from stdClass::__invoke() callback mocks were fixed in REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. tests. See ticket #53844 for more details.
The timeout for GitHub Actions jobs was lowered so runaway or stalled processes don’t risk running for the default timeout duration of six hours. See ticket #53363 for more details.
Date/Time, General, I18Ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks
@jeffpaul asked how we are progressing on the Pre Beta 1 tasks and asked if there are any items that need help.
@hellofromTonya replied that there are some Dev notesdev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:
a description of the change;
the decision that led to this change
a description of how developers are supposed to work with that change.
Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. that need to be compiled and published.
@audrasjb has been marking tickets that need Dev notes.
@mkaz noted that documentation for WordPress 5.9 could use some help and posted a link to the requirements. Contributors are invited to reach out to @mkaz with any questions.
@jeffpaul is working on the WordPress 5.9 HelpHub page.
@abhanonstopnewsuk noted that the latest checks for the About and Help page were carried out on Monday November 22, 2021. The next check is on Monday November 29, 2021 at 20:30 UTC.
@audrasjb will be leading a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub on November 25, 2021 at 21:00 UTC. See the 5.9 Bug Scrub schedule.
With Thanksgiving taking place in the US on November 25, 2021, @hellofromTonya thanked the community for all contributions.
Props to @costdev for writing the devchat summary.
After a call for volunteers, I’m pleased to announce that the new CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for 2022 (and beyond) is Mary Baum (@marybaum)!
Mary Baum
Mary is the owner of RacquetPress. She is a self-taught developer, and she is a woman of many talents and hobbies: from online fabric, product design, 3D to landscape and macro photography. She is a self-proclaimed tennis bum.
Mary has been part of multiple release squads in different roles since 2019. She is also the maintainer of two components, Help/About and Quick/Bulk Edit.
I, @francina, am stepping down and @audrasjb will continue until another team representative is found. Do not hesitate to reach out to him or ask in #core if you have questions about the role.
I am excited to see Mary stepping into the role and helping Core with all the adminadmin(and super admin) tasks needed to keep the team moving.
WordPress 5.9 will feature a brand new default theme named Twenty Twenty-Two. It arrives during an exciting time for WordPress themes. With the advent of Full Site Editing and Global Styles, themes are changing structurally and functionally to enable far more avenues for customization than users have come to expect in the past. To take advantage of these new abilities, Twenty Twenty-Two has been designed to be the most flexible default theme ever created for WordPress.
A reliable starting point
To find inspiration for this theme’s design, I did not have to look far. Thanks to a bird feeder attached to the outside of our kitchen window, my family’s daily breakfast routine involves a rotating cast of cardinals, doves, finches, jays, and tufted titmice. The birds are always up to something interesting: Sometimes they’re lining up patiently to take turns eating, other times they’re playfully performing aerial gymnastics.
While the birds’ exact behavior is unpredictable, they are remarkably reliable overall. The exact lineup changes somewhat, but every single morning there’s a group of birds eating breakfast with us. Throughout all of the tumult the world has seen in the past couple years, this consistent, entertaining routine has been a welcome starting point to my day.
That routine is the inspiration for this years’ default theme. Like the birds, Twenty Twenty-Two is designed to be light and resilient, with a hint of playfulness. The theme uses the lightweight Source Serif Pro for headlines, paired with a sensible sans-serif for support. Its color palette is drawn from nature, and layout elements sit gently on the page.
Above all, the theme is designed to be reliable. Its design choices are intentionally subtle, and its foundation will be built strong. It’s our hope that this theme will suit your site through many seasons.
Endlessly customizable
Twenty Twenty-Two will take advantage of a wide networknetwork(versus site, blog) of page templates, headers, footers, and other patterns so that users can easily make the theme their own. In another nod to the behavior of birds everywhere, these will offer a balance between fun and utility: some are irregular and unpredictable, while others are straightforward and traditional. Together, these patterns will act as a window into all of the possibilities that the theme enables.
In addition, Twenty Twenty-Two will ship with a range of alternate color schemes so that folks can drastically change the appearance of their site. Users will also be able to change fonts, image treatments, and more on a site-wide level. These new controls open up a wide array of drastically different customizations for the theme:
Twenty Twenty-Two is designed with the acknowledgement that its default appearance is not most people’s endpoint. Everyone deserves a truly unique website, built on a solid, well-designed foundation, and Twenty Twenty-Two aims to help them achieve that.
Built for Full Site Editing
To take advantage of these new customization features, Twenty Twenty-Two will be built for Full Site Editing first. The theme aims to use as little CSSCSSCascading Style Sheets. as possible: our goal is for all theme styles to be configured through theme.jsonJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. and editable through Global Styles. The theme development team will work closely with GutenbergGutenbergThe 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/ contributors to build design tools in the blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor that enable this goal.
As a block theme, Twenty Twenty-Two will likely require WordPress 5.9 to run. If the Twenty Twenty-Two and 5.9 release leads determine that there is need in the community for broader theme support, we will explore ways to bridge that gap.
Next steps
Kjell Reigstad (@kjellr) is leading design for Twenty Twenty-Two, and Jeff Ong (@jffng) is leading development. The two of us are looking forward to your involvement and support though the process! If you are interested in contributing to Twenty Twenty-Two, make sure you are following this blogblog(versus network, site).
Theme development will happen on GitHubGitHubGitHub 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/. Once the theme is stable, it will be merged into CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and its GitHub repo will be deprecated. An empty repository has been created here that you can follow if you’d like:
Starting on Monday October 11th at 3:00 PM UTC, there will be weekly SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. meetings in #core-themes to coordinate development of the theme.
The future of default themes
The community has produced a dozen best-in-class themes together, and we’ve come to look forward to a new one arriving at the close of each year. That said, themes are in a transition period today, and it seems like this may be a reasonable time to step back and to re-evaluate the annual cadence with which we build default themes.
Innovations like theme.json, block templates, and block patterns are making theme development far simpler, and are providing new ways for users to customize their sites. There’s reason to believe that the community can leverage all this to build more frequent and diverse theme and customization solutions for our users in the coming years.
We’re all still navigating these new opportunities (and in the meantime, we have a theme to build!) so let’s regroup after the 5.9 release to discuss future paths forward for default themes.
Learn more
For information about about previous default themes, you can read the following posts:
@adamsilverstein shared an update for the Image focus. The group plans to go through the ideas in this document to discuss the impact, level of difficulty, etc. and generally prioritize our work. Also, in addition to taking some time during the regular media meeting, the group members are proposing a regular second “performance image focus” meeting in a friendly timezone to APEC contributors. The first try for that meeting will be November 25, 2021, at 02:00 UTC.
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus
The JavaScript focus update was shared by @gziolo. The team is still collecting ideas for issues to work on in this document. They also discussed during the last week during #core-js office hours how to bring ES Modules and Import Maps to WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. The next office hour, focused on issues prioritization is planned on next Tuesday.
@wp-source stated that the team has some interesting projects ideas. Now, there is a need for some short and regular sync chat for the focus group members to discuss this project. If you are interested in attending one of these chats, please share your interest in this thread on Slack.
WordPress has historically relied on feature plugins to test future WordPress core features “in the wild”. The proposal here is to follow that approach, however by creating modules in a single “performance features wrapper pluginPluginA 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”.
By centralizing these efforts in 1 plugin instead of x plugins, the hope is to significantly reduce maintenance, encourage cross-collaboration between different performance efforts, and have a centralized place for any performance-related conversations.
For example, a central GitHubGitHubGitHub 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/ repository could be used to open issues with new performance enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas, discuss them etc, even if they don’t right away lead to a new performance module.
A single wrapper plugin also can help from an adoption perspective, essentially interested users can install the plugin once and then will get access to any new performance features as soon as they are added – they can then enable whatever they are interested in to try out.
There have been several discussions about where this repository should be created. The main locations being the Gutenberg repository, and under the GitHub WordPress organization.
After a vote, the repository has been created under the GitHub WordPress organization, and you can find it here.
A new date will be set for WordPress 5.9 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 so that 5.9’s exciting new features can be delivered in full, together with the intuitive, cohesive user experience. Beta 1 was originally scheduled for release yesterday and tentatively shifted to today to accommodate this. The overall schedule will be updated to reflect this and give contributors more time to collaborate further on the release.
Why postpone the beta?
WordPress has a specific philosophy of development. Its contributors follow the process that deadlines are not arbitrary. Schedules can shift if the results demand it.
Any changes to the proposed timetable are and must be carefully considered, as changes impact users preparing for the release and contributors contributing time and energies to make it happen.
As WordPress is open-source software, you can follow the discussion in real time on the release squad channel in the Make WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. group.
There are some others items too. These items could affect the 5.9 Release Candidaterelease candidateOne 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). (RC) and, likely, the final release. So it is better to allow time to focus on them at this stage.
How long of a delay?
The information that surfaced several hours ago suggests two to three weeks of focused work will produce a significantly better 5.9 version—much better than would a set of quick fixes intended to meet the current schedule.
The release squad is pulling together a revised schedule. Of course, given timezones, the discussion started before some members of the global team were awake for the day. So not every member has had a chance to weigh in. A proposed schedule is pinned in the 5.9 release-leads Slack channel. This proposal could change during the next 24-48 hours.
When will the Beta 1 release happen?
The current best guess is a two-week delay with an additional beta added to the cycle.
What will that do to the rest of the 5.9 release cycle schedule?
Again, please refer to this proposed schedule. A delay in the schedule also has to work with holidays, the end of the year, and the start of 2022.
As always, please add your thoughts to the comments on this post or the Slack discussion. Thank you for everyone’s feedback so far. Together, let’s continue to make WordPress better and better.
GutenbergGutenbergThe 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/ 12.0.0.
Navigation BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience..
Mobile Team.
Task Coordination.
Open Floor.
If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:
If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
You must be logged in to post a comment.