WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #44851, comment 2


Ignore:
Timestamp:
08/28/2018 09:25:53 AM (12 months ago)
Author:
hlashbrooke
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #44851, comment 2

    initial v1  
    1 Isn't this already the case with older version of WordPress anyway? If you have a site on an older major release branch (e.g. 4.2.x) and have auto-updates switched on for minor, but not major, releases (which is the default in WordPress if I'm not mistaken), then you will continue to receive back-ported security and maintenance updates even if you don't upgrade to the next/latest major release.
     1~~Isn't this already the case with older version of WordPress anyway? If you have a site on an older major release branch (e.g. 4.2.x) and have auto-updates switched on for minor, but not major, releases (which is the default in WordPress if I'm not mistaken), then you will continue to receive back-ported security and maintenance updates even if you don't upgrade to the next/latest major release.~~
    22
    3 I still get notifications about auto-updates for old client sites and one of them is currently in v4.2.21 as it has been steadily receiving security and maintenance updates for years,  even though it hasn't moved beyond the 4.2.x branch.
     3~~I still get notifications about auto-updates for old client sites and one of them is currently in v4.2.21 as it has been steadily receiving security and maintenance updates for years,  even though it hasn't moved beyond the 4.2.x branch.~~
    44
    5 If that's all true, then all that needs to happen for someone to be on a 4.9 LTS release is to just not run the update to 5.0. If we wanted to commit to that, then we could add an option to hide major update notifications I suppose, but in effect the work here is already done as it stands right now.
     5~~If that's all true, then all that needs to happen for someone to be on a 4.9 LTS release is to just not run the update to 5.0. If we wanted to commit to that, then we could add an option to hide major update notifications I suppose, but in effect the work here is already done as it stands right now.~~
    66
    7 I'm not a core dev by any means, but that seems to be the case as far as I can tell.
     7~~I'm not a core dev by any means, but that seems to be the case as far as I can tell.~~
     8
     9Ugh - just read your last paragraph properly, so my comment is moot :p
     10
     11I kind of agree with @jeremyescott on this one then - installing the Classic Editor plugin is effectively doing exactly what you're proposing, is it not?