Closed mbrodala closed 5 years ago
As you may have seen there we don't test, nor even develop, with v9:
I guess the declaration in composer.json was a bit over-ambitious (to allow other users to try to install it and figure out if it works at all). But realistically, development for v9 will not happen at least before the LTS, and most likely even months later, because we don't have the resources to do anything earlier.
Do you have documentation about the removal of typo3/cms-lang and possible migration path ?
In that case the compatibility with TYPO3v9 should probably be removed again until it is properly tested. Also typo3/cms-lang
should then probably be removed to ensure cross-version compatibility.
As for the LanguageService
please see the core changelog.
@PowerKiKi can you have a look at this?
Thank you for pinging me.
I took a a few minutes to plan a v4 which would only support a single LTS of TYPO3 (because of increased complexity introduced by core). So for now it would be TYPO3 9. This would allow to clean up our code from all compatibility hacks and be clearer in supported versions.
Unfortunately I still cannot afford much time on this project, and even though I'll try to spend a bit more time on it in the coming weeks, I cannot give you any ETA for that v4.
I can fully understand. Would it be possible to add this change and make a new 3.x release? Right now this package cannot be installed if only typo3/cms-*
packages are required.
Released as 3.3.2
Thanks a lot! :-)
This is considered good practice and allows for installing only the really necessary parts of TYPO3. Also starting with TYPO3v9 it is impossible to install "typo3/cms".
There is no "typo3/cms-lang" package anymore in TYPO3v9. This fact alone makes the currently declared full support of TYPO3v9 questionable.