X-post: AI Guidelines for WordPress

X-comment from +make.wordpress.org/ai: Comment on AI Guidelines for WordPress

WordPress 6.9.1 RC1 is now available

WordPress 6.9.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 (RC1) is available for testing! Some ways you can help test this minor 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.:

  • Use the WordPress Beta Tester 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.
    • As this is a minor RCrelease 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). release, select the 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. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in 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..
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.9.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.9.1 RC1 is a release candidate for a maintenance release with a focus on bugs introduced in WordPress 6.9. In total, this RC features fixes for 23 issues throughout Core and 25 for the Block Editor.

WordPress 6.9.1 is led by @jorbin and @wildworks.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets are included:

  • #63979 – WordPress Core setup does not configure XDebug properly
  • #64229 – Enqueueing scripts, styles, and script modules should warn when dependencies are missing
  • #64329BlockBlock Block 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. Processor tests fail without intl extension
  • #64333I18Ni18n Internationalization, 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.: border.radiusSizes key is missing in theme-i18n.jsonJSON JSON, 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.
  • #64336 – One removed SimplePie file was not added to `$_old_files` in WP 6.9
  • #64337 – Broken styling on “Add Plugins” screen
  • #64340HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. may double-escape class names when adding repeatedly
  • #64347 – Fatal error when `wxr_cdata()` is called with non-string value
  • #64348 – The `$embeds` element is missing from the `wp_mail_succeeded` filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.
  • #64350 – checkbox not working as expected in the adminadmin (and super admin) panel
  • #64366 – Docs: Replace since x.y.z with actual version number
  • #64368 – `Could not instantiate mail function` errors sending mail in 6.9
  • #64380 – Widgets sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and position can’t be changed with 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) mode enabled
  • #64412 – Sporadic unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. failure in Tests_REST_WpRestUrlDetailsController::test_get_items
  • #64429 – Script Modules: Dependencies inherit fetchpriority from not-enqueued, registered modules
  • #64462 – Update Sodium Compat to 1.24.0
  • #64474 – Comments: Notes are accessible when query has comment_type=all
  • #64485 – WP_Block_Processor should indicate that inner HTML matches no block type.
  • #64531 – assertEqualHTML may ignore leading whitespace text
  • #64537 – Block Processor: Extracting full block missing nested content.
  • #64535 – Update packages for 6.9.1
  • #64354 – Outlined buttons now have grey background
  • #64136PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Deprecated: Fetching multiple feeds with single SimplePie instance is deprecated since SimplePie 1.9.0

The following 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/ PRs are included:

  • #71123 – iAPI: Fix and refactor runtime initialization logic
  • #72376 – Fix Popover closing unexpectedly when a Menu inside it is closed.
  • #73046 – Notes position alignment in HTML
  • #73580 – Gutenberg plugin: Override core classic theme styles
  • #73592 – Block Editor: Restore ToolSelector component for backward compatibility
  • #73608 – Accordion Heading: Add default style for classic themes
  • #73612 – Block JSON schema: add visibility key to supports definition
  • #73835 – Color Panel: Ensure minimum height for popover content
  • #73865 – Classic Block: Restore HTML editing option
  • #73867 – Block API: Fallback to all attributes when checking for unmodified block
  • #73955 – Global Styles: fix infinite loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop in Font Style UIUI User interface
  • #74130 – Terms Query Block: Fix Max terms for non-hierarchical taxonomies
  • #74177 – Fix: Prevent accordion-heading submitting/sending forms (button type=”button” )
  • #74282 – Fix: menu_order validation to allow zero and negative values
  • #74580 – iAPI: Update deprecation warning for unique ID format
  • #74715 – Media & Text: Revert “Fixed Media & Text Block – Image not rendered properly on frontend when inside stack”
  • #74057 – Blocks: Always trigger borwser console warnings for blocks with apiVersion below 2
  • #74340 – Fix parent popover not closing on click outside
  • #74750 – iAPI Router: Prevent router regions with data-wp-key from being recreated on navigation
  • #74857 – iAPI Router: Fix initial router regions with attachTo being duplicated after navigate()
  • #74860 – Fix: Fit Text not working on calculated line heights.
  • #74864 – Fix: Safari “Edit as HTML” for Fit Text deletes content
  • #74927 – Patterns: restore pattern categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. actions for user patterns
  • #73652 – Fix: Stretchy text issue when nested on flex containers.
  • #74799 – [WP 6.9.1] Remove formatting controls restriction private API

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.9 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, February 3, 2026. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.orgWordPress.org The 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/ 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/ #6-9-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.9.1 depends on proper testing, so please lend a helping hand.

Props @wildworks, @joedolson, @westonruter for pre-publication review.

Summary, Dev Chat, January 28, 2026

Start of the meeting in 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/, facilitated by @audrasjb 🔗 Agenda post.

Announcements 📢

Nominations for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps 2026

The nomination process for Core Team Representatives for 2026 is still open. Please submit your nomination here.

Recap: WordPress 6.9 “Gene” Retrospective

A retrospective of WP 6.9 was published by its release squad, with detailed feedback on the 6.9 cycle.

WordPress 6.9.1 Release Schedule

The WordPress 6.9.1 maintenance release is planned on February 3, 2026, with a first BetaBeta A 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. release on January 29, 2026.

@jorbin noted that help is still needed on the following tickets/PR:

WordPress 7.0 Release Squad and Bug Scrub Schedule

The WordPress 7.0 Release Squad has been announced.

The 7.0 bug scrub schedule was published. @audrasjb hosted the first scrub right before the devchat.

What’s new in 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/ 22.4

Gutenberg 22.4 was released, with a detailed announcement.

Open floor 💬

As a new contributor @indigochill asked whether ticketticket Created for both bug reports and feature development on the bug tracker. #60726 was a good way to start contributing to WordPress Core. @johnbillion, @jorbin and @audrasjb confirmed that it is a nice first ticket to learn how to contribute to Core as it is self-contained and clearly documented, but encouraged them to thoroughly read all the comments in the ticket to make sure to understand the full background of the ticket and its history.

#6-9-1, #7-0, #core, #dev-chat

X-post: Should 1024-bit certificates be removed from the root certificate bundle?

X-comment from +make.wordpress.org/hosting: Comment on Should 1024-bit certificates be removed from the root certificate bundle?

Dev Chat Agenda – January 28, 2026

The next WordPress Developers Chat will take place on Wednesday, January 28, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

Nominations for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps 2026

The nomination process for Core Team Representatives for 2026 is still open. Please submit your nomination here.

Recap: WordPress 6.9 “Gene” Retrospective

A retrospective of WP 6.9 was published by its release squad, with detailed feedback on the 6.9 cycle.

WordPress 6.9.1 Release Schedule

The WordPress 6.9.1 maintenance release is planned on February 3, 2026. See the release schedule announcement for more information.

WordPress 7.0 Release Squad and Bug Scrub Schedule

The WordPress 7.0 Release Squad has been announced.

The 7.0 bug scrub schedule was published.

What’s new in 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/ 22.4

Gutenberg 22.4 was released, with a detailed announcement.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#6-9, #6-9-1, #7-0, #agenda, #core, #dev-chat

Bug Scrub Schedule for WordPress 7.0

It’s time to get WordPress 7.0 ready for release, and help is needed to ensure it’s smooth and bugbug A 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome! 🎉

Schedule Overview

Regular bug scrubs are being held twice a week with @audrasjb and @juanmaguitar leading them. As the release date approaches and activity ramps up, the number of scrubs may be increased. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!

Continue reading

#7-0, #bug-scrub, #core, #core-test, #props

Performance Chat Summary: 27 January 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared a Trac query covering performance-related tickets milestoned for WordPress 6.9.1 and 7.0.
  • @westonruter shared that for ticketticket Created for both bug reports and feature development on the bug tracker. #61500, some work was done recently as part of the CodeMirror upgrade effort.
    • @westonruter explained that ideally there would be a declarative way to add script modules as dependencies for classic scripts, and noted that a workable approach is to register an empty script module that declares module dependencies, and then enqueue that module whenever the classic script is enqueued. @westonruter shared reference to example diffs demonstrating this workaround and mentioned being glad to find a quick solution.
  • @mukesh27 asked whether @westonruter had reviewed the latest comment on #64229, where @wildworks raised a minor point and opened a PR.
    • @westonruter replied that the comment had been seen the night before and initially mentioned not having a 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. yet, then noted that a PR already existed and shared PR #10799. @westonruter reviewed the PR, said it looked good, and approved it.
  • @westonruter brought up #64066 and shared that @gilbertococchi is actively working on collecting data to support switching to moderate prefetch by default on sites with caching.
    • @westonruter referenced a Slack thread where LCP passing rates for conservative versus moderate prefetch were discussed and noted that additional data is being gathered by flipping a few CrUX-eligible sites from conservative to moderate to compare LCP passing rates and page hit increases over time.
    • @westonruter added that landing #64066 is related to #64370, noting that the latter needs to land to ensure reliable detection.
  • @mukesh27 asked about the review status of PR #10606 and mentioned seeing comments from @westonruter.

Performance Lab 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. (and other performance plugins)

Open Floor

  • @westonruter shared recent experience using 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 by the repository owner. https://github.com/ Copilot together with Gemini CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. locally, describing it as immensely useful both for review and implementation work. @westonruter described Copilot as significantly better than a traditional linter during reviews and noted that it can provide strong first-pass implementations. @westonruter shared PR #10778 as an example of using Gemini CLI during the CodeMirror upgrade and explained that a detailed historical and technical specification was provided to the tool.
    • @westonruter also shared that Copilot was used to draft a Performance Lab fix while on public transit using only a phone, referencing PR #2346.
    • @dmsnell cautioned that Copilot can sometimes reintroduce defects during PR reviews, sharing an anecdote where Copilot repeatedly flagged and reintroduced a PCRE-related bugbug A 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. even after it had been fixed.
    • @justlevine added that this behavior can indicate ambiguities in code and suggested that improving self-documentation helps both humans and LLMs.
    • @dmsnell emphasized the need for extra care when LLMs introduce defects, as they can confidently repeat mistakes if the surrounding code does not change enough.
    • @westonruter agreed, noting that while hallucinations occur, the tools still provide good feedback most of the time and help shift focus away from minutiae like coding standards toward higher-level problem solving.
  • @dmsnell raised the topic of memoizing wp_normalize_path, noting observed performance improvements of roughly 1ms during WordPress startup in certain environments. @dmsnell explained that while this is a micro-optimization, it can have meaningful impact at scale and shared that @josephscott has been investigating early startup costs using production measurements. @dmsnell mentioned having tested earlier versions without caching and discussed trade-offs between caching and alternative approaches, including replacing PCRE calls and addressing what may be a latent bug.
    • @westonruter asked whether similar performance benefits were observed across different approaches.
    • @dmsnell replied that while direct testing had not yet been done for all variants, prior comparisons suggested the cache provided most of the benefit at a fraction of the cost, and that both approaches could potentially coexist.
    • @westonruter summarized this as a “both/and” situation rather than an either/or choice.

Our next chat will be held on Tuesday, February 10, 2026 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

X-post: Call for Testing – Customizable Navigation (“Mobile”) Overlays

X-post from +make.wordpress.org/test: Call for Testing – Customizable Navigation ("Mobile") Overlays

Summary, Dev Chat, January 21, 2026

Start of the meeting in 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/, facilitated by @desrosj 🔗 Agenda post.

Announcements 📢

Nominations for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps 2026

The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.

Dropping support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3

Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0. More details are available in this post.

7.4 is currently at ~22% of all WP sites. So let’s find ways to work with Hosts and site owners to decrease that number.

WordPress 6.9.1 Release Schedule

The WordPress 6.9.1 maintenance release is planned on February 3, 2026. See the release schedule announcement for more information.

@jorbin shared this update: “Just a general note that here are multiple scrubs being held each week (see the 6.9.1 announcement). If you want to join for one of those or feel free to work on any of the tickets in tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or 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 by the repository owner. https://github.com/ in your own time. You may see pings on those tickets, if you are able to help it would be appreciated as we work to resolutions on these. No concerns as of now, we seem to be in good shape for a release on 3 February.”

#6-9-1, #7-0, #core, #dev-chat

Recap: WordPress 6.9 “Gene” Retrospective

This post summarizes the feedback received from the WordPress 6.9 retrospective. Thank you to those who contributed their feedback via the retrospective survey and comments on the post!

For ease of reading, feedback has been synthesized. Full feedback is available for review in the anonymized form responses and comments to the original post.

Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation. 

What would you keep?

  • Having two triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads in different parts of the globe seemed to work well getting more contributors involved.
  • Clearer test instructions.
  • Long-term planning, regular check-ins, commit freeze, and a consistent cadence made the release feel stable and well-managed.

What would you add?

  • More automation for defined, common steps within the release cycle could help reduce stress.
  • Better documentation for the tasks required by the different release leads.
  • More community suggestions into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Earlier on boarding for release squad members.

What would you change, reduce, or remove?

  • Release Candidates should be tested more extensively.
  • Points of contact and ownership should be more clear, especially for new contributors.
  • Reduce manual work by increasing automation where possible.

What else would you like to express about any part of the release cycle or release squad?

  • The 6.9 release was well coordinated despite its size and complexity, reflecting significant effort from contributors and release leads.
  • There is a need for better communication with teams indirectly involved with the release, especially Documentation.
  • Releasing during a major event (SOTW in this case) was exciting but can limit who is able to take part due to various logistical factors (travel funds, VISAs, time differences, etc). Also requires planning further in advance.
  • The release squad was highly collaborative. Leads were trusted to complete the work required of their role.
  • Lots of contributors and committers were around and made themselves available to answer any questions the squad members had.
  • Tracking and guiding all release-related activity across TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and 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 by the repository owner. https://github.com/ is a huge undertaking due to the volume of activity. This can place a lot of strain on the team.

Did you have an official role on the release squad during the 6.9 release?

This section describes if the survey participants are part of release squad or observer.

Did you contribute to the 6.9 release?

This section describes if the participants actually contributed to 6.9 release or not.

How did collaborating on this project feel?

This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.

Would you like to be part of future release squads?

  • 17.6%: I haven’t been part of a release squad and currently have no interest in it.
  • 11.8%: I haven’t been part of a squad but I would like to try in the future.
  • 5.9%: I have been part of a release squad but will not repeat in the near future.
  • 67.4%: I have been part of a release squad and I will gladly repeat

What is your feedback on the current release squad size?

Takeaways and next steps

  • Find ways to assemble and onboard a squad for the next release earlier.
  • Review the Core Handbook for missing documentation.
  • Figure out how to make responsibilities for release-related tasks more clear.
  • Investigate how parts of the release process could possibly be automated.
  • Find new ways to encourage wider testing during the betaBeta A 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./RCrelease 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). period.
  • Make it more clear which contributors are knowledgeable and available to help for specific tasks or areas of the project.
  • Pairing up an experienced and inexperienced contributor in each role is a good way to “level up” those who are looking to participate in a release squad for the first time.

Props to @akshayar & @desrosj for compiling responses, authoring, and @jeffpaul, @jorbin for reviewing this post. 

#6-9, #retrospective