WordPress.org

Make WordPress Core

Opened 13 months ago

Last modified 5 weeks ago

#38419 new feature request

Make beta testing an opt-in feature in core

Reported by: mor10 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.7
Component: General Keywords: has-ux-feedback has-ui-feedback
Focuses: Cc:

Description

Currently beta testing of WordPress core (and feature plugins) is something you have to be aware of to take part in. This limits the reach of beta testing feedback to those who are intimately engaged in the day-to-day development of WordPress core and results in feedback that skews heavily in the direction of those who build WordPress as opposed to those who use WordPress.

To increase participation in end-user testing of WordPress core and feature plugins, active participation in such programs should be surfaced more visibly, either through settings during install, a modal pop-up, or an alert.

To be clear, I'm not talking about testing of bleeding edge nightlies here, but specific features and feature plugins in Beta or RC state.

A simple admin alert saying "WordPress 4.7 beta is available. Would you like to test it?" would be a huge improvement. Similar can be done with select feature plugins, especially if the alert is tied to the feature they change/improve (so for a new media feature, the alert would appear when the media functionality is engaged: "We are working on a new and improved media panel. Would you like to test it?").

This would of course have to be done sparingly to avoid alert overload.

Simplified feedback procedure

Along with the surfacing of beta testing, there should be a way to provide feedback on features directly from within WordPress admin. Asking for feedback to be posted in a Trac ticket or even a Make blog post limits the number of possible responses significantly. An in-app feedback feature activated only for testers would greatly simplify the process and most likely increase the volume of feedback data significantly. Whether this data is mapped to Trac tickets or something else needs to be addressed.

Change History (11)

This ticket was mentioned in Slack in #design by mor10. View the logs.


13 months ago

#2 @mor10
13 months ago

Related: #38418

#3 @celloexpressions
13 months ago

Even making the Beta Tester plugin one of the featured plugins on add-new would be an improvement here. I like the idea of making the existence of beta versions more prominent.

#4 @rmccue
13 months ago

Huge +1 on the feedback procedure; we have no integrated feedback process at all right now.

#5 @karmatosed
13 months ago

Good idea. A few thoughts come to me:

  • Settings come to mind as a good place over a modal or pop-up which aren't great experiences.
  • I think a MVP is an information block somewhere saying beta available. From there we can build.
  • We should show the information we get back if we do have feedback, make it available but anonymous to all.

#6 @karmatosed
13 months ago

  • Keywords ux-feedback ui-feedback added

#7 follow-up: @celloexpressions
13 months ago

What about a new metabox on the dashboard? We could include a button to install the beta tester plugin from there, and possibly update that plugin to default to nightly builds (or a way to only do betas, instead of trunk).

#8 in reply to: ↑ 7 @swissspidy
13 months ago

What about a new metabox on the dashboard? We could include a button to install the beta tester plugin from there, and possibly update that plugin to default to nightly builds (or a way to only do betas, instead of trunk).

Related: #23348, #33007.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


5 weeks ago

#10 @karmatosed
5 weeks ago

There is now a precedence for this after #41316, it's a good idea and something we should work on as a MVP having what we do for Gutenberg.

#11 @karmatosed
5 weeks ago

  • Keywords has-ux-feedback has-ui-feedback added; ux-feedback ui-feedback removed
Note: See TracTickets for help on using tickets.