[wp-trac] [WordPress Trac] #49923: Change "Critical Issue" to "Recommendation"

[WordPress Trac]

#49923: Change "Critical Issue" to "Recommendation"
--------------------------+------------------------------
 Reporter:  La Geek       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Site Health   |     Version:  5.4
 Severity:  critical      |  Resolution:
 Keywords:  close         |     Focuses:
--------------------------+------------------------------

Comment (by Clorith):

 Ahh, let me dive in a bit deeper then :)

 The `WP_AUTO_UPDATE_CORE` constant can have 3 values: `true`, `false` and
 `minor`.

 Depending on your install type, these values can have different behaviors,
 which I suspect is what led to this ticket. It should be noted that they
 will also change the descriptive text depending on that scenario

 On a normal site (not using an early access version like beta or trunk),
 these are the statuses:
 - `true` - Status is considered `Good`
 - `minor` - Status is considered `Good`
 - `false` - Status is considered `Critical`

 Critical text:
 > WordPress security and maintenance releases are blocked by `define(
 'WP_AUTO_UPDATE_CORE', false );`.

 So on a normal site, having it set to allow minor updates, or all updates,
 is perfectly fine.

 On an early access site, such as beta or trunk, these are the statuses:
 - `true` - Status is considered `Good`
 - `minor` - Status is considered `Critical`
 - `false` - Status is considered `Critical`

 Critical text:
 > WordPress development updates are blocked by the `WP_AUTO_UPDATE_CORE`
 constant.

 The same rings true for the filters that can be used to block updates,
 they also have specific texts to identify if it's blocking minor updates.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49923#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform