Post by account_disabled on Mar 10, 2024 4:29:56 GMT
Incompatible developments before they were even born. While for some developers skipping major versions once made sense, for the reasons mentioned above it will be easy to stay on track and aligned with core release cycles and version control which means website owners starting on can be sure Do you want to upgrade to or wait as future updates will eliminate the need to rebuild and migrate the site once they are on or higher. Therefore there is a need to discuss community support for until sometime in 2020 or 2020. I think it makes sense to start this discussion now and announce a date for this year to give users maximum time to support. Plan your updates. There are rumors that core support will end on the date of the major release but since to will.
Be incremental changes and future releases will be scriptable it seems like it's time to launch. Countdown ahead. If year or year seems too early, remember that there are still sites on , more than seven years since launch and more than two years since official end of life. It is also possible that a similar situation will arise where the Long Term Support (LTS) plan will apply regardless of when support is officially withdrawn. The C Level Contact List current plan requires providers to release all security patches released publicly to the community for free so there will still be support options and security patch support even after expiration. So what does the timeline look like? The release timeline could end up looking like this. Release numbers are just examples. All of this is just to start a conversation about these topics. We're still discussing things like key recipients and basics with the security team. Proposals and will be supported after one year. In summary and will be supported.
For one year after release, after which and are expected to be migrated to . Because it will be easier to migrate from to than from to and we can set the expiry date in advance. The final support time may be longer than that. Alternative proposal Support ends one year after Support ends two years after . The release schedule is in principle as follows: year month year month year month The official support period for each major version totals five years. Each version with will have support extended for three years. Other instances may have a three-year support cycle or no time commitment in particular. So in order to benefit from security support for as long as possible we ideally need to release a major version within months of each major release. This would give us official security support for about four years. Beyond that, future releases may look like this. When synchronized with the timeline, this means that each major version has a development.
Be incremental changes and future releases will be scriptable it seems like it's time to launch. Countdown ahead. If year or year seems too early, remember that there are still sites on , more than seven years since launch and more than two years since official end of life. It is also possible that a similar situation will arise where the Long Term Support (LTS) plan will apply regardless of when support is officially withdrawn. The C Level Contact List current plan requires providers to release all security patches released publicly to the community for free so there will still be support options and security patch support even after expiration. So what does the timeline look like? The release timeline could end up looking like this. Release numbers are just examples. All of this is just to start a conversation about these topics. We're still discussing things like key recipients and basics with the security team. Proposals and will be supported after one year. In summary and will be supported.
For one year after release, after which and are expected to be migrated to . Because it will be easier to migrate from to than from to and we can set the expiry date in advance. The final support time may be longer than that. Alternative proposal Support ends one year after Support ends two years after . The release schedule is in principle as follows: year month year month year month The official support period for each major version totals five years. Each version with will have support extended for three years. Other instances may have a three-year support cycle or no time commitment in particular. So in order to benefit from security support for as long as possible we ideally need to release a major version within months of each major release. This would give us official security support for about four years. Beyond that, future releases may look like this. When synchronized with the timeline, this means that each major version has a development.