Update inline documentation for `auto_update_{$type}`

[desrosj]

The inline documentation for the auto_update_{$type} filter says:

Generally speaking, plugins, themes, and major core versions are not updated by default, while translations and minor and development versions for core are updated by default.

This is no longer accurate. As of 5.6, new installations are set to auto-update for major versions as well as minor (see [49581], and the ​related Making WordPress Core post).

The inline docs here should be updated to state that installs created prior to 5.6 will not auto-update major versions, but new installs on 5.6 and higher will. It would also be good to scan the rest of the update related files and confirm that the inline docs for other filters and actions accurately reflect this change.

The inline docs for auto_update_{$type} should be updated to state that installs created prior to 5.6 will not auto-update major versions, but new installs on 5.6 and higher will.

Trac ticket: https://core.trac.wordpress.org/ticket/53330

[felipeloureirosantos]

Adding the new comment here as well in case there are improvements on the text:

Before version 5.6, the plugins, themes, and major core versions were not updated by default. New installs on 5.6 and higher will only not update plugins and themes by default, while translations and core (minor, major, and development) are updated by default.

[audrasjb]

I'd suggest this wording:

 * Before version 5.6, plugins, themes, and major core versions were not updated by default.
 * New installs on 5.6 and higher will automatically update translations and core (minor,
 * major, and development versions). Plugins and themes are still updated manually by default.

[marybaum]

Per Slack conversation https://wordpress.slack.com/archives/C02RQBWTW/p1637270022045500

Before version 5.6, someone had to do manual updates to plugins, themes, and major versions of Core. As of version 5.6 and to this day, all those updates can happen automatically, if you choose. All you do is check an action link on the appropriate page in the WordPress Admin.

[audrasjb]

@marybaum thank you!

However, as it is not a user facing string, but a documentation accessible only to those checking the source code of the function, I don't think we should use "you" (and directly talk to the reader of the docs). It's not an end-user docs but rather an information to bring more context on the default values for these hooks :)

[marybaum]

Replying to audrasjb:
So we can say, "All anyone needs to do ..." or "All a site admin needs to do ... "

@marybaum thank you!

However, as it is not a user facing string, but a documentation accessible only to those checking the source code of the function, I don't think we should use "you" (and directly talk to the reader of the docs). It's not an end-user docs but rather an information to bring more context on the default values for these hooks :)

[desrosj]

Replying to marybaum:

Per Slack conversation https://wordpress.slack.com/archives/C02RQBWTW/p1637270022045500

Before version 5.6, someone had to do manual updates to plugins, themes, and major versions of Core. As of version 5.6 and to this day, all those updates can happen automatically, if you choose. All you do is check an action link on the appropriate page in the WordPress Admin.

I’d also argue that this is inaccurate. Automatic updates for major updates, plugins, themes, and translations have possible since WordPress 3.7 by using filters or constants. The only thing that changed in 5.6 is that an interface was introduced.

How about: “Minor and development versions for Core, as well as translations are auto-updated by default. Starting in WordPress 5.6, major updates are also applied automatically by default, and users can opt-in to auto-updates for plugins and themes.”

Since this is developer documentation, it should be precise and to the point.

[davidbaumwald]

Replying to desrosj:

Replying to marybaum:

Per Slack conversation https://wordpress.slack.com/archives/C02RQBWTW/p1637270022045500

Before version 5.6, someone had to do manual updates to plugins, themes, and major versions of Core. As of version 5.6 and to this day, all those updates can happen automatically, if you choose. All you do is check an action link on the appropriate page in the WordPress Admin.

I’d also argue that this is inaccurate. Automatic updates for major updates, plugins, themes, and translations have possible since WordPress 3.7 by using filters or constants. The only thing that changed in 5.6 is that an interface was introduced.

How about: “Minor and development versions for Core, as well as translations are auto-updated by default. Starting in WordPress 5.6, major updates are also applied automatically by default, and users can opt-in to auto-updates for plugins and themes.”

Since this is developer documentation, it should be precise and to the point.

+1 This is for developers and should be very straightforward and technically focused. I think @desrosj 's recommendation is the one that should be used.

[felipeloureirosantos]

I added the last comment mentioned, but looks like that I did something wrong, as I see a big diff now with all the changes that were added when I selected to fetch upstream. I would love if you folks could confirm, as I'm not an experienced dev.

* Minor and development versions for Core, as well as translations are
* auto-updated by default. Starting in WordPress 5.6, major updates
* are also applied automatically by default, and users can opt-in to
* auto-updates for plugins and themes.

[desrosj]

@felipeloureirosantos Did you happen to use rebase? I usually perform a pull into my branches because GitHub will show you the entire diff for PRs after rebasing.

No worries though. I can take the patch for the changed file when committing!

I am going to make one more revision of this before committing. The new description does not indicate that installs created before 5.6 can choose to opt-in to auto-upates for major releases in 5.6 or newer. Going to roll with this:

"Minor and development versions for core, as well as translations have been auto-updated by default since WordPress 3.7. New installs on WordPress 5.6 or higher will also auto-update major versions by default. Starting in 5.6, older sites can opt-in to major version auto-updates and auto-updates for plugins and themes."

[desrosj]

In 52214:

Upgrade/Install: Improve the accuracy of the auto_update_{$type} filter docblock.

This updates the filter documentation for auto_update_{$type} to account for the changes to default auto-update behaviors made in WordPress 5.6.

Starting in WordPress 5.6, all new installs auto-update major versions by default.

Props felipeloureirosantos, audrasjb, marybaum, davidbaumwald.
Fixes #53330.

[desrosj]

In 52215:

Docs: Remove instances of the “eg.” abbreviation in favor of “example” or “for example”.

See #53330.

Final implementation was committed in https://core.trac.wordpress.org/changeset/52214.