-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Preparing for next release, v1.10 #4356
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
Comments
Is there any chance of revisiting #3591? This is an issue which crops up periodically on the forum. The merit of PyPi is simplicity for new users. Consider a new user of the Pyboard running Windows. To use upip they need to create a Linux VM, clone the MicroPython repo and compile the Unix build. These may be major hurdles. I can't see how to write a single upip version which is both highly optimised for ESP8266 and is OS-agnostic. If it can be done, it should be. There is a definite need for some solution to this problem. |
i also get the same problem of esp8266, which uart(0) dont works neither with dupterm(None,1) nor dupterm(None) |
@hwt9520 can you please expla 8000 in in more detail the problem? What version of the esp8266 firmware did you use, what is the code that you run, and what is it you expect to happen? If your issue is the same as (or related to) what is described in #4314 then please post the details in that issue. |
esp8266-20180511-v1.9.4.bin thank you for help me |
I'd like to see #3658 resolved, even if it's just duplicating the ESP8266 docs and correcting any errors. I can put some time into the docs over the holiday period if that fits in with the 1.10 schedule. And if I were to pick any single defect to have resolved it would be #4269. It really undermines the quality of the ESP32 port. I know it's not trivial though... Glad to see a release plan though! Thanks @dpgeorge |
I'm looking forward to a release so that bugs fixed long ago (#3153) find their way into an official release build. I'm not alone in coding round that one. As for the CoC I don't know how effective it is likely to be in practice. But if it helps towards a greater level of tolerance towards beginners and those whose experience differs from our own I'm all for it. I think skilled people have a duty to share with those younger or less experienced while remaining willing to learn. Someone might be a less skilled Python coder yet have relevant knowledge and experience which they lack. Just my two penn'orth :) |
Thanks all for the feedback. I have added the requested 3 issues to the list and will try to get to them. |
Thanks for all of you to help us solve the problem! |
@dpgeorge I guess you are already aware of the Loboris ESP32 port. Is there any chance to bring such features right into this main repo? Most notably: sdcard support, wear leveling and OTA partitions. Or, is there any plan for any other enhancement to the ESP32 port? I see the port is pretty young and it also has nightly builds only (sign that it's still in an early stage). |
We may also want to consider addressing #4396 for v1.10? This issue has stung more than half of the people I've introduced to MicroPython on the ESP32... |
There're more and more comments appear on tickets/PRs "this should be addressed after 1.10". But what's being done to make that release? There're no comments here for a while. And the list contains strange items like:
How adding code of conduct relates to the release? CoC deals with community interaction, while a release is well, a release. Adopting CoC in non-fiat way usually requires collecting community feedback, which requires time. Making that process deadlock the release is again, strange. |
Oh, and btw, the release should be good enough reason to get response to #4363. |
You can see that the list at the top is being updated with items as they are completed (and discussion happens in those issues/PRs). Now that a majority of the items are done I'm happy to make the release ASAP, in the interest of moving forward. Following earlier release numbering, the next one will be v1.10 and not v1.10.0 as previously stated. |
Builds have all been checked, relevant tests run, and release notes are being prepared. |
👍 Waiting eagerly @dpgeorge |
v1.10 is tagged at 3e25d61 |
Remaining items were done: GitHub release made, esp-extra-scripts branch rebased and force-pushed, micropython.org/download updated (ordering of some firmware is funny but that will go away in time), and docs updated. |
…l_flash add GD25Q16C flash to BlackPill
Uh oh!
There was an error while loading. Please reload this page.
There have been many commits since v1.9.4 and it's definitely overdue for the next release. There have been many changes so it's beyond v1.9.5, but the code is not yet ready for v2.0, so v1.10.0 makes sense.
PRs/issues to try and resolve before the release are:
The text was updated successfully, but these errors were encountered: