[wp-trac] [WordPress Trac] #51978: Add 'development' as accepted vaue for WP_AUTO_UPDATE_CORE

[WordPress Trac]

#51978: Add 'development' as accepted vaue for WP_AUTO_UPDATE_CORE
-----------------------------+-----------------------------
 Reporter:  knutsp           |      Owner:  (none)
     Type:  enhancement      |     Status:  new
 Priority:  normal           |  Milestone:  Awaiting Review
Component:  Upgrade/Install  |    Version:  5.6
 Severity:  minor            |   Keywords:
  Focuses:                   |
-----------------------------+-----------------------------
 > knutsp
 > The 'beta' and 'rc' strings was added to WP_AUTO_UPDATE_CORE constant.
 Why was
 > 'nightly' not added, too?

 > dd32 2020-12-09 05:04
 > That’s a good question :slightly_smiling_face:  The main reasoning I
 didn’t think > of even adding it was because if you install a nightly, it
 stays on nightly
 > forever, there’s no need to opt-in through the constant.
 > Beta/RC is more complicated as it’s running stable, but augmenting it
 with
 > Beta/RCs.
 > https://core.trac.wordpress.org/changeset/49245/trunk/src/wp-
 includes/update.php > could be added to also allow for development or
 branch-development for
 > nightly/branch nightlies.
 > The whitelist for that parameter on the dotorg side is: [ 'beta', 'rc',
 'stable', > 'development', 'branch-development' ]

 https://wordpress.slack.com/archives/CULBN711P/p1607486676211300

 So I propose this to be implemented, at least 'development'. Reasons:
 1. Completeness
 2. Possibility to run a testing site, running latest development version
 ("nightly builds"), without the Beta Tester plugin.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51978>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform