# A New Testing Channel Cannot Fix an Unclear Testing Ask ## Claim Adding another pre-release channel cannot produce useful feedback when contributors still lack a clear, specific description of what to test. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source:** [[3. Resources/Readwise/Articles/Core Committers Meeting – WordCamp Europe 2026]] > [!quote] > "Most of the discussion so far was acknowledged to be a technical solution to a communications problem." WordPress core committers discussed a Chrome-style Canary channel while the Beta Tester plugin had roughly 3,000 active installs and experiment enablement remained difficult. The proposed distribution surface could increase exposure, but the meeting's own diagnosis was that contributors first need earlier communication, a simpler activation path, and a concrete testing ask. ## Scope & conditions - Applies when a project already has a path to pre-release software but receives too little actionable feedback. - Does not reject new release channels where access itself is the demonstrated bottleneck. - A clearer ask still needs a safe activation and rollback path; communication does not remove the risk of irreversible database migrations. ## Links - [[Open Source Governance MOC]] — locates testing-channel design within contributor coordination and release governance. - [[3. Resources/Permanent Notes/A Findable Resource Beats a Warning Broadcast at the Unready]] — extends: both replace broad announcement volume with specific information available when a contributor is ready to act. - [[3. Resources/Permanent Notes/Default-Off Feature Flags Decouple Shipping Speed From Production Risk]] — contrasts: a feature flag controls exposure risk, while a testing ask determines whether that exposure yields useful evidence. - [[3. Resources/Permanent Notes/Advocacy Converts on the Specificity of the Ask Not the Force of the Indictment]] — extends: contributors act on a bounded request more reliably than on a general appeal for participation. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: release-channel design governs how a distributed contributor project recruits and interprets testing evidence. ## Source - [[3. Resources/Readwise/Articles/Core Committers Meeting – WordCamp Europe 2026]] — primary meeting recap for the Canary proposal, feedback gap, and communication diagnosis.