Pin setup to only use luma.core v1.x.y lineage #128
Merged
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
thijstriemstra
requested changes
Oct 24, 2020
thijstriemstra
approved these changes
Oct 24, 2020
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.
I want to introduce a breaking change in luma.core to improve performance. This will mean changing how the fullframe and diff-to-previous framebuffers work. I intend releasing that breaking feature as a 2.x.y release.
In order to be able to roll that out without breaking this project, we need to set the install_required to not upgrade luma.core to the 2.x.y release.
Shortly after luma.core 2.x.y is released, this package will be upgraded to use the improved framebuffer.