-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for version bump to 0.6 #65
Comments
@nia-e you might find interesting things to upstream from here https://github.com/nviennot/lvgl-rs/commits/master |
Lovely, thanks! I'll try to work this into the next release then, especially the LVGL update. Might delay #64 more for this. |
Is there anything else worth doing before we publish 0.6.0? I took a look at #25 but it doesn't seem exceedingly urgent (might make the API a little neater I suppose, so I could do that). For #32, I don't have access to a Windows machine |
I could write more docs, I suppose - especially on |
@rafaelcaricio can I bump to 0.6.0 and release? Or are there more things you'd like to see done first? A lot has been updated and other than #82 I don't foresee any real breaking changes happening soon (and that's still a ways off and will require a lot of discussion to get to a final, mergeable state) |
@nia-e go for it! ;) |
What are the outstanding things to do before bumping to 0.6.0? #51 will be an API-breaking change and so a semver bump will be needed. What else should be added/fixed/reworked?
My ideas thus far:
lv_drivers
intolvgl-sys
#64Maybe:
lvgl-rs
#68 <=> Close Consider moving boilerplate into its own module/crate? #24The text was updated successfully, but these errors were encountered: