Task #77708
closed
Added by Mathias Brodala over 7 years ago.
Updated over 6 years ago.
Description
The TYPO3 development/release cycle could be changed to follow semver
This would mean reliable release versions with 100% guarantee of no breaking changes in patch and minor releases. Currently breaking changes also go into minor releases up until the next LTS.
hey mathias,
we decided on going an approach closer to fear-driven versioning, and since the TYPO3 Core is in my opinion still a box of cowboyed code which has no clear line (a lot of "public" properties in a class, which would be breaking if we remove them) with code that is 12ys old and wasn't touched (!) since then, I can say that semver does not fit (yet) to our code base of the core. So currently the approach documented here https://typo3.org/teams-committees/core-development/resources/release-lifecycle/ makes the most sense for developers, LTS release strategy and communication to clients as well extension authors.
- Status changed from New to On Hold
Thanks for the clarification and especially the reference to ferver. I still dislike breaking changes in minor releases but I fully understand your points and why semver does not (yet) make sense for TYPO3.
I'll put this ticket on hold for now. ;-)
- Category set to Miscellaneous
- Status changed from On Hold to Accepted
- Target version set to Candidate for Major Version
Current plans are: try to avoid breaking changes in 9.1-9.x, and see if that works out, then we can introduce proper semver in v10.
- Status changed from Accepted to Closed
I will close this ticket for the time being, as this is more organizational than adding a patch, marking it as "resolved".
Thanks for starting to move in this direction. :-)
Also available in: Atom
PDF
Updated by 
Updated by