10000 Timing of next release? · Issue #6017 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

Timing of next release? #6017

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.

Sign up for GitHub

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

Jump to bottom
Closed
jonsmirl opened this issue May 7, 2020 · 5 comments
Closed

Timing of next release? #6017

jonsmirl opened this issue May 7, 2020 · 5 comments

Comments

@jonsmirl
Copy link
jonsmirl commented May 7, 2020 •
edited
Loading

The current release (not master) of micropython is using the commit id of the ESP32 beta 4 SDK. At the time this release was made esp32 support had compile issues. Those issues were quickly fixed in micropython master, however the release tag is in front of those fixes. lv_micropython is only ported to releases of micropython so those build issues got ported into lv_micropython.
https://forum.littlevgl.com/t/esp32-micropython-build-errors-lots/1754

These issues can be fixed with a few edits, but a new micropython release would cure the problem by moving onto the released ESP32 4 SDK.

Note: if you install the ESP compiler using the ESPIDF3 method you won't encounter this. If you install the compiler using the new install script in ESPIDF4 you'll hit it.
@dpgeorge
Copy link
Member
dpgeorge commented May 8, 2020

We don't have a scheduled release timeline (maybe we need one...) and because everything is done on the master branch it can be hard to coordinate working towards a release and adding new features (maybe that workflow needs to change...).

Regardless, there does need to be a new release sooner rather than later. And I'd like it to be very soon.

@tve
Copy link
Contributor
tve commented May 8, 2020 •
edited
Loading

IMHO it would be nice to get the various TLS and non-blocking socket fixes which culminate in adding TLS to uasyncio into MP for the next release.. E.g. #5819 is ready and there are several more lined up behind it.

@embeddedt
Copy link
embeddedt commented May 12, 2020 •
edited
Loading

Is the master branch considered stable enough at any point in time to work off of? Perhaps lv_micropython should just use that instead. relevant LittlevGL forum post by jonsmirl

(cc @amirgon - not sure if you're already watching this or not)

@dpgeorge
Copy link
Member

Is the master branch considered stable enough at any point in time to work off of?

The master branch is the development branch, so at any given commit it may have new bugs or regressions. But the tests are extensive and get very good coverage, and the CI covers a lot, so master is usually quite stable.

@amirgon amirgon mentioned this issue Jul 6, 2020
Closed
tannewt added a commit to tannewt/circuitpython that referenced this issue Feb 15, 2022
@tannewt
Merge pull request micropython#6017 from weblate/weblate-circuitpytho…
160b1aa 
…n-main

Translations update from Hosted Weblate
@jonnor
Copy link
Contributor
jonnor commented Jul 3, 2024

There has been many releases since 2020! This issue can be closed

@jonsmirl jonsmirl closed this as completed Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jonsmirl @tve @jonnor @dpgeorge @embeddedt
0