[Documentation] Improve and fix the release cycle documentation #13903
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was quite surprised when I found out that our release cycle is called time-based in our documentation 馃槺 That's definitely not the way we are releasing Sylius now (and it has not been for some past versions as well).
So, to improve transparency within the Community, I would like to document what are the factors we take into consideration when planning the new minor release and what are the consequences of this decision.
I've also remodelled the tables with past releases a little bit 馃拑
Do not fear, the 1.12 release date will be determined soon 馃殌 馃枛