drop backward compatibility of settings + run forward compatibility only once #58250
Conversation
This file contains 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
2 tasks
|
Any chance to speed up the required review process through a donation to the qgis project? |
nyalldawson
approved these changes
Aug 1, 2024
|
Many thanks, 50 € are on the way |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #57671
! This is for the release 3.34 branch !
If we merge this, we need to take the same approach in the new releases too.
I don't think it makes a lot of sense to keep updating settings fro 3.30 and older since 3.34 is now the LTR. We can do the same approach (migrate only once) in new releases so moving directly from 3.28 to 3.40 would work (which is probable in big organisations).