[wp-trac] [WordPress Trac] #58371: Could you please backport the [55504] patch to the 6.1 branch?

[WordPress Trac]

#58371: Could you please backport the [55504] patch to the 6.1 branch?
---------------------------+----------------------
 Reporter:  hassy6thsense  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  closed
 Priority:  normal         |   Milestone:
Component:  General        |     Version:
 Severity:  normal         |  Resolution:  wontfix
 Keywords:                 |     Focuses:
---------------------------+----------------------
Changes (by audrasjb):

 * keywords:  needs-patch =>
 * status:  new => closed
 * version:  6.1.1 =>
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 Hello and welcome to WordPress Core Trac, thanks for opening this ticket,

 Sorry but only security fixes are backported to previous releases.
 Previous branches should not really be considered as “maintained”.

 "Officially WordPress only provides support for the latest version of the
 software. The Security team historically has a practice of backporting
 security fixes as a courtesy to sites on older versions in the expectation
 the sites will be automatically updated"
 [https://make.wordpress.org/security/2022/09/07/dropping-security-updates-
 for-wordpress-versions-3-7-through-4-0/ (source)]

 Also we can not backport fixes based on individual requests, it would
 quickly get impossible to manage, and we would probably end up maintaining
 several branches of the CMS :)

 > There is no function to turn off automatic maintenance update for
 WordPress, and I don't want to turn it off for security reasons.

 Actually, [https://wordpress.org/documentation/article/configuring-
 automatic-background-updates/#constant-to-disable-all-updates there is an
 option] to turn off auto-updates for minor releases, but I wouldn't
 recommend it either.

 > I still need to use 6.1 because some of the plugins I use have not yet
 announced support for 6.2.

 I think the point is that these plugin authors probably forgot to update
 their readme to indicate compatibility. This happens frequently. The best
 would be to contact them via each plugin's support forum and ask them to
 confirm the compatibility of their plugin.

 Let's close this ticket as `wontfix`, since there is no plan to backport
 maintenance fixes to older branches.
 Thank you for understanding!

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