| 6 | | > 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 |
| 7 | | > forever, there’s no need to opt-in through the constant. |
| 8 | | > Beta/RC is more complicated as it’s running stable, but augmenting it with |
| 9 | | > Beta/RCs. |
| 10 | | > 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 |
| 11 | | > nightly/branch nightlies. |
| 12 | | > The whitelist for that parameter on the dotorg side is: [ 'beta', 'rc', 'stable', > 'development', 'branch-development' ] |
| | 5 | > 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. |
| | 6 | > |
| | 7 | > Beta/RC is more complicated as it’s running stable, but augmenting it with Beta/RCs. |
| | 8 | > |
| | 9 | > 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. |
| | 10 | > |
| | 11 | > The whitelist for that parameter on the dotorg side is: [ 'beta', 'rc', 'stable', 'development', 'branch-development' ] |