Hint for abandoned core extensions

[mhuber84]

Sometimes core extension get removed or merged into other extension. If you want to know why this happened, you have to search in the breaking changes for the extension key (not package name!). A litte hint for this would be very helpful.

[gilbertsoft]

Reading the Core change log before a major upgrade is not a nice to have but a must!

I'm not sure how the download portal could solve this...

[mhuber84]

Just a little hint at the bottom of this page would be very helpful: https://get.typo3.org/misc/composer/helper

[gilbertsoft]

This would end up in a mess imho.

I guess in the first place you should change your major update workflow. If you use the composer helper during the upgrade to select the core packages to upgrade you will automatically struggle over the missing packages which then you remove before the new require command for the upgrade.

If you like to have a better explanation how to do a major upgrade you should create an issue at the docs or directly provide a proposition e.g. for the page https://docs.typo3.org/m/typo3/guide-installation/10.4/en-us/Upgrade/InstallTheNewSource/Index.html, use the edit button at the top to directly provide a PR.

[mhuber84]

This would end up in a mess imho.

Why?

I guess in the first place you should change your major update workflow. [...]

I know.

If you like to have a better explanation how to do a major [...]

A hint on this page would have saved some hours of searching. And perhaps would save this time for others to.

[gilbertsoft]

This would end up in a mess imho.

Why?

Well the Core team tries to make things easier and reduce the list of core packages and on the other hand you like to list this packages again, that's what I mean

If you like to have a better explanation how to do a major [...]

A hint on this page would have saved some hours of searching. And perhaps would save this time for others to.

We are planing other tools here which should make the upgrade path easier, also for upgrades from non composer installs and migration to composer installs. That's imho the way to go.

I like to keep this issue open in the mean time until we have a solution here.

Thanks for the hint.