[TASK] Add description why and when TYPO3 updates should be performed #583
Conversation
Resolves: #451 Releases: main, 13, 12
|
|
||
| Log file rotations | ||
| ================== | ||
|
|
There was a problem hiding this comment.
Content seems to be missing here?
| have to update the third party extensions too. In the **TYPO3 Extension Repository (TER)** you can enter the name of | ||
| that extension and get information about supported TYPO3 versions. You find the TER `here <https://extensions.typo3.org/>`__. | ||
| You will recognize that some extension developers stopped developing their extension further. We recommend that you only | ||
| use third party extensions that are still supported. |
There was a problem hiding this comment.
How can a user find out, if an extension is still supported? Is it, when an official release ist uploaded to TER? Some Extension authors prefer to only publish on packagist.
|
|
||
| .. _getting-started-cronjobs: | ||
|
|
||
| Cron jobs |
There was a problem hiding this comment.
I do not understand, in which context this chapter refers to TYPO3 updates?
|
|
||
| .. _getting-started-logfile-rotations: | ||
|
|
||
| Log file rotations |
There was a problem hiding this comment.
I do not understand, in which context this chapter refers to TYPO3 updates?
|
|
||
| .. _getting-started-sys-log: | ||
|
|
||
| Sys log |
There was a problem hiding this comment.
I do not understand, in which context this chapter refers to TYPO3 updates?
| version of TYPO3 CMS currently available on the market. It has the newest security features and the | ||
| most amount of useful features. That is why you should always want to have your | ||
| TYPO3 instances on the newest version possible. Another advantage is that you get free security fixes. |
There was a problem hiding this comment.
Not every new major version comes with new security features. So I think, the main benefit from using a current TYPO3 version is, that it receives free bugfixes and free security patches for at least 3 years from the time of the first LTS minor release.
|
|
||
| In the following we look a bit deeper into the types of updates. Otherwise, when you feel safe with the concepts you | ||
| can use the :ref:`Upgrade Guide <t3coreapi:upgrading>` as a general or later reference to perform updates. | ||
|
|
There was a problem hiding this comment.
I think, we could summarize in a small chapter the following:
- When a new major LTS version is released, users should focus on updating to this version ASAP
- When a new minor version is released, users must update to the new minor version, since the previous minor version is not supported any more
- When a new patch level version is released, users should always update to the new version, because it contains important bugfixes and security fixes (if announced)
Additionally, users should take care of updated extensions on a regular schedule in order to use the most recent versions.
Resolves: #451
Releases: main, 13, 12