5.x: remove 3.x and 4.x version change info blocks #7565
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LordSimal
commented
Jan 5, 2023
| ./4-3-migration-guide | ||
| ./4-4-migration-guide | ||
| ./4-5-migration-guide | ||
| >>>>>>> 4.next |
There was a problem hiding this comment.
seems there was a little merge conflict left in the 5.x branch 😄
|
AuthComponent, Shells etc. have been deprecated since 4.0, so there no need to retain any info regarding them in 5.x docs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This removes (nearly) all occurrencies of
.. versionadded::.. versionchanged::.. deprecated::related to old 3.x and 4.x version changes.
Nearlybecause I kept "removed features" pages likeas they are because I don't know if we wanna
I would prefer to just remove the whole page (as well as the referene to it in the menu of course) but just wanted to ask what you think
This would then be handled in a separate PR if we agree upon that.