WordPress 7.0 Release Candidate 3  🔗 **Source:** [WordPress 7.0 Release Candidate 3](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/) > [!note]+ Document Notes > tags: #wordpress #software-release #testing #development > author: Amy Kamala > source: WordPress.org News > reference: https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/ > date created: 2024-12-19 14:30 > > # 🏷️ Title: WordPress 7.0 Release Candidate 3 > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Test RC3 on staging environments — Final release scheduled May 20, 2026 #testing - [H2] Update plugin/theme "Tested up to" version to 7.0 — String freeze now in effect #development - [H3] Review Real Time Collaboration feature changes — Postponed to v7.1 cycle #feature-planning ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress 7.0 Developer Notes](https://make.wordpress.org/core/wordpress-7-0-developer-notes/) - [WordPress Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/) ## 📝 Summary - WordPress 7.0 Release Candidate 3 is available for testing with final release scheduled for May 20, 2026 - Real Time Collaboration feature has been removed from 7.0 and postponed to the 7.1 release cycle - RC3 addresses 143+ issues since RC2 and represents the string freeze milestone for translations - Community testing is crucial across hosting platforms, themes, and plugins before production release - Multiple testing methods available including Beta Tester plugin, direct download, WP-CLI, and WordPress Playground ## 📖 Main Content WordPress 7.0 Release Candidate 3 represents a critical milestone in the major version release cycle. As the third release candidate, it indicates the software is approaching production readiness but still requires extensive community testing to identify potential issues. The announcement emphasizes that this is development software not suitable for production sites. Testing should occur on staging environments using one of four methods: the WordPress Beta Tester plugin, direct download, WP-CLI commands, or the browser-based WordPress Playground. A significant development is the removal of Real Time Collaboration functionality from the 7.0 release. This feature will be re-evaluated for inclusion in the 7.1 cycle, demonstrating WordPress's commitment to shipping stable features rather than rushing incomplete functionality. The RC3 milestone also marks the string freeze point, meaning no new translatable strings will be added. This allows the internationalization community to complete translations for the final release across 100+ supported languages. ## 🗒️ Notes #### Release Timeline and Status - Key milestone: Third release candidate indicates near-final software - Final release: Scheduled for May 20, 2026 - String freeze: Now in effect for translation teams #### Testing Methods Available - WordPress Beta Tester plugin: Select "Bleeding edge" channel and "Beta/RC Only" stream - Direct download: ZIP file installation on test sites - WP-CLI: `wp core update --version=7.0-RC3` command - WordPress Playground: Browser-based testing with no setup required #### Major Feature Changes - Real Time Collaboration: Removed from 7.0 scope - Issue resolution: 143+ tickets closed since RC2 - Re-evaluation timeline: RTC targeted for 7.1 release cycle #### Community Contribution Areas - Testing: Bug reporting through support forums or WordPress Trac - Translation: Hard string freeze enables final localization work - Plugin/Theme compatibility: Update "Tested up to" version to 7.0 - Hosting platform validation: Distributed testing across infrastructure providers #### Testing Infrastructure - Known participating hosts: Kinsta, Bluehost, GoDaddy, WordPress.com, XServer, Ionos - Support channels: #core-test Slack channel, Make Core blog - Bug reporting: Alpha/Beta support forums or direct Trac tickets ## 📚 References - [WordPress 7.0 Release Schedule](https://make.wordpress.org/core/7-0-release-schedule/) - [WordPress Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/) - [WordPress 7.0 Developer Notes](https://make.wordpress.org/core/wordpress-7-0-developer-notes/) - [WordPress Trac](https://core.trac.wordpress.org/) - [Make WordPress Core Blog](https://make.wordpress.org/core/) ## 🗣️ Paraphrase - WordPress 7.0's third release candidate is available for community testing before the May 20, 2026 final release - The Real Time Collaboration feature has been postponed from version 7.0 to 7.1 to ensure quality and stability - Testing can be done through multiple methods including plugins, direct downloads, command line tools, or browser-based environments ## 📰 Newsletter WordPress 7.0 Release Candidate 3 is here! 🚀 The WordPress community is in the final stretch before the major 7.0 release on May 20, 2026. RC3 brings us closer to a stable release with 143+ bug fixes since the last candidate. **Key Update:** Real Time Collaboration features have been moved to the 7.1 release cycle, demonstrating WordPress's commitment to shipping polished functionality. **How to Help:** Test RC3 on your staging sites using the Beta Tester plugin or WordPress Playground. Plugin and theme developers should update their "Tested up to" versions and validate compatibility. **Translation Teams:** The string freeze is now in effect - perfect timing to complete localizations for the 100+ supported languages. Resources: [Beta Tester Plugin](https://wordpress.org/plugins/wordpress-beta-tester/), [WordPress Playground](https://playground.wordpress.net/), [Developer Notes](https://make.wordpress.org/core/wordpress-7-0-developer-notes/) ## ✅ Action Items #### WordPress - Core: Validate RC3 testing feedback, triage critical bugs before final release - Community: Coordinate testing sprints, support forum moderation for RC3 issues - Training: Update lesson plans for 7.0 features, prepare release training materials - Documentation: Finalize 7.0 DevHub updates, review HelpHub content gaps - Polyglots: Complete translations during string freeze, coordinate language pack releases - Meta: Prepare .org infrastructure for 7.0 release traffic, update download systems - CLI: Test WP-CLI 7.0 compatibility, update command documentation - Hosting: Coordinate with hosting partners for release day preparation - Plugins: Review compatibility reports, communicate breaking changes to developers - Themes: Validate theme compatibility testing, update review guidelines #### Community - Contributors: Join testing efforts through #core-test Slack channel - Maintainers: Test plugins/themes with RC3, update compatibility metadata - Sponsors: Support testing infrastructure and release coordination efforts #### OSPO - Software Inventory: Update SBOM for 7.0 release components - Security Management: Review RC3 security fixes and vulnerability disclosures - Community Engagement: Coordinate with hosting partners for distributed testing ## 🧪 Hypotheses - RC3 testing will identify fewer critical issues than previous release candidates due to maturity - Real Time Collaboration removal will reduce overall release risk and improve stability - String freeze timing will enable higher quality translations for major languages - WordPress Playground testing will increase community participation in release validation ### 📊 Methodology - Community testing feedback analysis through support forums and Trac tickets - Hosting partner distributed testing results comparison across platforms - Translation completion metrics across supported language packs ### ❓ Questions - What specific issues led to Real Time Collaboration being postponed to 7.1? - How will the RTC architecture testing with hosting partners influence 7.1 development? - What testing coverage metrics indicate readiness for final 7.0 release? ### 🔮 Future Research - Real Time Collaboration technical requirements for hosting compatibility - Release candidate testing effectiveness measurement and optimization - Community-driven testing incentive programs and participation metrics ### 💡 Implications - Practice: Plugin and theme developers need RC3 testing before May 20 deadline - Policy: String freeze demonstrates mature release process governance - Security: RC3 testing validates security fixes before production deployment - Education: Testing process documentation needs updates for community participation - Funding: Release coordination requires sustained investment in testing infrastructure ### 🧠 Learning Styles Assessment Reading level estimate: 10th Grade (technical content with clear explanations) #### 👀 Visual learners - Present: Clear release timeline, testing method options - Improve: RC testing workflow diagram, feature comparison charts #### 🔊 Aural learners - Present: Not available in current format - Improve: Audio announcement summary, podcast discussion of changes #### 🗣️ Verbal learners - Present: Clear definitions of RC3, string freeze, testing methods - Improve: Analogies for release process stages, glossary expansion #### 🧩 Kinesthetic learners - Present: Multiple hands-on testing methods, WordPress Playground - Improve: Step-by-step testing checklists, interactive testing scenarios #### 🧠 Logical learners - Present: Release timeline, numbered testing steps, ticket tracking - Improve: Testing decision trees, bug severity classification #### 🧑‍🤝‍🧑 Social learners - Present: Community testing calls, Slack channels, forum discussions - Improve: Testing buddy system, group testing events #### 🧘‍♀️ Solitary learners - Present: Individual testing options, self-guided documentation - Improve: Personal testing journals, self-assessment checklists #### 🌿 Naturalistic learners - Present: Organic community contribution process - Improve: Release ecosystem analogies, collaborative development metaphors ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive link text - Improve: More descriptive alt text for any testing interface screenshots #### Keyboard navigation - Present: Standard web navigation patterns - Improve: Skip links for testing tool interfaces, logical tab order #### Contrast and readability - Present: Standard WordPress.org theme contrast ratios - Improve: Ensure code examples maintain sufficient contrast #### Text resizing and reflow - Present: Responsive WordPress.org theme - Improve: Test at 200% zoom for technical content readability #### Media and captions - Present: Text-based announcement - Improve: Captions for any future video testing guides #### Forms and interactions - Present: Basic subscription form with labels - Improve: Clear error messaging for testing tool downloads #### Standards reference - WordPress.org generally meets WCAG 2.1 AA standards ### 🌍 DEIB Assessment #### Cultural breadth - Present: 100+ language translation support mentioned - Improve: Highlight global community testing contributions #### Inclusive language - Present: Gender-neutral technical language, clear terminology - Improve: Plain language alternatives for technical jargon #### Neurodiversity support - Present: Multiple testing method options, structured content - Improve: Consistent heading frequency, bullet point formatting #### Representation - Present: Diverse community contribution acknowledgment - Improve: Highlight contributors from different backgrounds and regions #### Psychological safety - Present: Encouraging tone for community participation - Improve: Explicit welcome for new testers, failure-safe testing guidance ### ✅ Logical Validity #### Strong reasoning - Deductive strength: RC3 position in release cycle implies near-final status - Inductive strength: Previous testing feedback improves final release quality - Causal reasoning: String freeze enables translation completion - Analogical strength: RC process parallels other major software releases #### Fallacies - Appeal to tradition: "As always, testing remains crucial" - assumes past necessity applies without justification - False urgency: Release date pressure could compromise thorough testing evaluation #### Tone of voice - Overall tone: Professional and encouraging with clear technical guidance and community appreciation ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on community or critics - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive community engagement, collaborative language throughout ## 🎯 Conclusion WordPress 7.0 RC3 represents a mature pre-release requiring focused community testing before the May 20, 2026 final release. The postponement of Real Time Collaboration to version 7.1 demonstrates responsible feature management prioritizing stability. Plugin developers, theme authors, and hosting providers should prioritize compatibility testing during this critical window. The string freeze enables translation teams to complete localization work for global users. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Release candidates require extensive community testing > [!quote] [WordPress 7.0 Release Candidate 3](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/) by [[Amy Kamala]] via [[WordPress.org News]]. Published May 8, 2026. Accessed December 19, 2024. > "Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible." WordPress emphasizes community testing as essential for release quality, providing multiple testing methods for different technical skill levels. [view highlight](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/#H1) #xref #articleseed ID:rw_wp70rc3_testing ### [H2] Feature postponement demonstrates quality commitment > [!quote] [WordPress 7.0 Release Candidate 3](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/) > "Real Time Collaboration will not be included in the 7.0 release and will be re-evaluated during the 7.1 release cycle." WordPress postpones major features to maintain release quality rather than rushing incomplete functionality to market. [view highlight](https://wordpress.org/news/2026/05/wordpress-7-0-release-candidate-3/#H2) #xref ID:rw_wp70rc3_rtc --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] String freeze enables translation completion - Applies to software with internationalization requirements - RC3 milestone timing allows 100+ language completion - Links: [[Release-Management]] [[Internationalization]] #### [Z2] Multiple testing methods increase participation - Browser-based, command-line, plugin, and direct download options - Reduces technical barriers for community involvement - Links: [[Community-Testing]] [[Developer-Experience]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research WordPress Playground testing capabilities — RC3 announcement #fleeting #inbox - [F2] Compare RC testing participation metrics across versions — WordPress.org data #fleeting #inbox - [F3] Document hosting partner testing coordination process — distributed testing #fleeting #inbox <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WordPress 7.0 Release Candidate 3.md|WordPress 7.0 Release Candidate 3 by wordpress.org]] ## Highlights - Thank you to the Hosts who helped test variations of new RTC architecture: Kinsta, Bluehost, GoDaddy, WordPress.com, XServer, and Ionos, and to [the hosts who participate in distributed testing](https://make.wordpress.org/hosting/test-results/) regularly. ([View Highlight](https://read.readwise.io/read/01kr6v9q25em7n5zzkjb5khyy3))