Skip to content

Preparing for next release, v1.11 #4784

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

Closed
4 tasks done
dpgeorge opened this issue May 14, 2019 · 13 comments
Closed
4 tasks done

Preparing for next release, v1.11 #4784

dpgeorge opened this issue May 14, 2019 · 13 comments

Comments

@dpgeorge
Copy link
Member

dpgeorge commented May 14, 2019

The last release was v1.10 on 26 Jan 2019. Since then there were around 350 commits, and big changes to the .mpy file format, so the plan is to make the next release v1.11.

Remaining issues/PRs to resolve before the release are:

Please mention any other issues/PRs that could fit in for this release.

@peterhinch
Copy link
Contributor

upip - Please ensure it can install library modules compatible with official MicroPython (either via an alternative version or a command line arg).

@pfalcon
Copy link
Contributor

pfalcon commented May 14, 2019

Please include correct copyright information about files I created or made substantial contributions to, as well as to the whole project, pull requests #4787 & #4363 .

@miketeachman
Copy link
Contributor

It would be great to have v1.11 in a condition to facilitate productive development with the new PYBD boards. I saw one PR #4669 related to this. Perhaps there are other issues and PRs that fit into this category? Are there step-by-step docs describing how to make a build?

What do you think? There will be a lot PYBDs coming into developer hands - it would be cool to make it easy for people to get started and contribute.

@nedoskiv
Copy link

It will be nice to have stable network.PPP module

@dpgeorge
Copy link
Member Author

It would be great to have v1.11 in a condition to facilitate productive development with the new PYBD boards.

The reason PYBD support is not merged yet is because I wanted that to be the focus of the next-next release (v1.12). The upcoming v1.11 already has enough new stuff in it, and merging big changes for PYBD will possibly lead to regressions to existing code which need time to be addressed. So in the interest of cutting a stable release ASAP, I don't want to merge any PYBD related items yet.

@dpgeorge
Copy link
Member Author

It will be nice to have stable network.PPP module

Unfortunately this is not possible right now. It's a really difficult thing and needs someone who has the hardware, expertise and time to look into making it work. If you can look into it yourself and make some progress improving it that would be really great.

@dpgeorge dpgeorge pinned this issue May 20, 2019
@mattytrentini
Copy link
Contributor

I'm not sure what kind of timeframe we're looking at but I intend to make a few improvements to the ESP32 docs in the next week. Mostly issues we noticed shortly after the 1.10 release. Shouldn't be a showstopper for 1.11 though.

@dpgeorge
Copy link
Member Author

I'm not sure what kind of timeframe we're looking at

A release is imminent.

@dpgeorge
Copy link
Member Author

Ok... v1.11 was tagged in 6f75c4f

@dpgeorge dpgeorge unpinned this issue May 29, 2019
@robert-hh
Copy link
Contributor

When updating the Download pages, please update the Pyboard D binaries too.

@dpgeorge
Copy link
Member Author

please update the Pyboard D binaries too.

Ok, that's now done. Docs are updated (except for a PDF build error, to be fixed) and esp-extra-scripts branch is force pushed.

@pfalcon
Copy link
Contributor

pfalcon commented May 30, 2019

Please include correct copyright information about files I created or made substantial contributions to, as well as to the whole project, pull requests #4787 & #4363 .

What's the reason for not including this in the release?

@bruno963852
Copy link
Contributor

Sorry if the question is dumb, but it is not possible to just use the gsm module done by loboris on his fork?

tannewt added a commit to tannewt/circuitpython that referenced this issue May 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants