WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#32613 closed enhancement (fixed)

Allow easy fallback to the latest stable release when beta testing with the beta tester plugin

Reported by: ryan Owned by:
Milestone: WordPress.org Priority: normal
Severity: normal Version: 4.2.2
Component: Upgrade/Install Keywords: beta-testing-flow
Focuses: Cc:

Description (last modified by ryan)

The Grand Unified Updater present a Re-Install Now button that allows reinstalling your site with the latest stable release. When using the beta tester plugin to test point release or bleeding edge nightlies, there is no such button. Let's add a "Return to Latest Stable Release" type button to allow a push button means of leaving the beta testing track. Some language warning that the database may have been altered in non-forward compatible ways by the nightlies is probably in order, although in practice our database changes are usually forward compat with old releases.

I think this will be strictly UI changes, with no backend heavy lifting required. The infrastructure behind Re-Install Now should be easy to reuse for "Return to Latest"

Related:

https://make.wordpress.org/core/handbook/beta-testing/
https://wordpress.org/plugins/wordpress-beta-tester/

Attachments (3)

Screen Shot 2015-06-11 at 10.50.51 AM.png (425.2 KB) - added by ryan 5 years ago.
Re-Install Now in the GUU
Screen Shot 2015-06-11 at 10.46.44 AM.png (507.9 KB) - added by ryan 5 years ago.
Add a Return to Latest Stable Release button here.
Screen Shot 2015-06-29 at 1.25.59 pm.png (180.4 KB) - added by dd32 5 years ago.

Download all attachments as: .zip

Change History (8)

@ryan
5 years ago

Re-Install Now in the GUU

@ryan
5 years ago

Add a Return to Latest Stable Release button here.

This ticket was mentioned in Slack in #core-flow by boren. View the logs.


5 years ago

#2 @ryan
5 years ago

  • Description modified (diff)

#3 follow-up: @dd32
5 years ago

That's what it looks like currently (with no core changes) if we simply return an update offering for latest along side the development update offering.

#4 in reply to: ↑ 3 @ryan
5 years ago

Replying to dd32:

That's what it looks like currently (with no core changes) if we simply return an update offering for latest along side the development update offering.

That looks very much like good enough. It reads understandably. Perhaps language that mentions returning you to the stable track would help, but the directness of simply offering 4.2.2 is nice. The visibility of this is only those who have opted onto the beta track. The entire page is a Boren placeholder design in need of a real designer, so, in the probable absence of design help, let's not sweat a somewhat ugly cluster of four buttons that is exposed only to beta testers . :-)

#5 @dd32
5 years ago

  • Milestone changed from Awaiting Review to WordPress.org
  • Resolution set to fixed
  • Status changed from new to closed

The entire page is a Boren placeholder design in need of a real designer, so, in the probable absence of design help, let's not sweat a somewhat ugly cluster of four buttons that is exposed only to beta testers . :-)

My thoughts exactly. I've had grand plans of getting that page redesigned and actually including the Beta Tester by default for ages now.

I've made the change in the API to return the extra package, if anyone see's any problems, re-open.

Note: See TracTickets for help on using tickets.