Extended Support Release (9 posts)

  1. chaoix
    Posted 3 years ago #

    Has the WordPress team ever thought of doing an extend support release of WordPress?

  2. esmi
    Forum Moderator
    Posted 3 years ago #

    What for?

  3. Laura Hedgecock
    Posted 3 years ago #

    That's a great idea. For support. I'm starting my site and have been waiting for 5 days for help (links won't show up), I don't understand how to re-size widget boxes. I wouldn't mind paying a fee to be able to have access to support.

  4. WPyogi
    Forum Moderator
    Posted 3 years ago #

    I don't think that's what the OP means, but if you want paid support, you can always consider hiring someone:


  5. chaoix
    Posted 3 years ago #

    What I meant is a version of WordPress that doesn't introduce new features, but does receive security updates. Other open source projects, such as Firefox and Ubuntu, offer such a release for corporate users looking for long term stability over the constant addition of new features.


    [No bumping, thank you.]

  6. To loop back around: Not at this time, since there is SO MUCH that needs to be done for improvement.

    One release might just be a clean up one day, now that we do 'themed' releases, but don't bank on it.

  7. The WordPress philosophy on LTS versions is LTS == Long Term Suckage

    I used to think this was valid, hence the 2.0 LTS branch. Now, after
    working with hundreds of the largest companies and media properties in
    the world, I am philosophically opposed.

    While I like the theory of LTS, what happens in practice is it covers up
    the incompetence of IT or developers because they put off small slightly
    painful upgrades until they get so out of date of trunk (3 years? 5
    years?) and you have to go through a giant, painful, screws everybody
    over upgrade.

  8. chaoix
    Posted 3 years ago #

    Thanks for the answer, Chris.

    I agree with the some of the things said in the article, but I definitely think Matt underestimates the time involved in constantly upgrading WordPress. In the corporate IT world, updates needs to be tested before you roll it out so you don't break custom code, etc.

    There are definitely pitfalls to a traditional years long LTS. I think an LTS with a year or year and a half life time would fit the WordPress development cycle well while meeting the needs of more WordPress developers.

  9. chaoix - I don't think he underestimates, since wordpress.com is running wordpress.org and has to update when we do :)

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.