Confusing development process
-
@danielm said in Confusing developmemt process:
Btw, did you try to build v1.20.0.rc0?
No. Not yet. I've seen a not that it seems to require esp-idf 3.1, and before I try, I want to be sure that there is a way back. Did you try it?
Edit: Failed at the first step, compiling the boot loader with the existing esp-idf
Edit2: Doinggit checkout idf_v3.1in pycom-esp-idf changed the game
-
@robert-hh
I totally agree with you. Release cycles should be more controlled and better documented. I think there was a promise of periodical releases including change logs few months ago...Btw, did you try to build v1.20.0.rc0?
-
@danielm I've seen it, and that caused me to write my post. Before that, there were lte-xykon, lte-attach-fix, socket-fix, nbiot-xykon. I would expect with every release a list of issues, that are fixed, a list of changes (v1.20.0.rc0 for instance uses resp. supports littlefs) and a list of open issues.
It's not that I could not sort that out by myself, at least partially, but in a proper development environment that information must be available. The git log serves not well for that purpose.
-
There is v1.20.0.rc0 in works which will probably contain recent fixes, at least it seems so according to commits:
https://github.com/pycom/pycom-micropython-sigfox/commits/v1.20.0.rc0
