Releasing Updates

[ayushsharma82]

Pretty sure you guys have already thought of this but just an opinion - Last release was more than a year ago. I think you should start releasing minor versions of this core with recent bug fixes and feature requests?

A OSS library like mine (NetWizard) is already waiting for the removable routes and webserver filters which were added recently ( but the update for core is yet to be released ), without the release I cannot add ESP8266 support.

[nopnop2002]

This is just my personal opinion.

it is possible that EspressIF is devoting a lot of manpower and time to supporting esp-idf and is hoping for a quiet demise for esp8266.

[JAndrassy]

@nopnop2002 this repository is not maintained by Espressif

[nopnop2002]

@JAndrassy

I misunderstood.

We look forward to the next master update.

[ayushsharma82]

@mcspr A beta release for now so that community can test and give us feedback before finally releasing all the fixes?

[mcspr]

@mcspr A beta release for now so that community can test and give us feedback before finally releasing all the fixes?

Git install is not an option? Both ArduinoIDE and PIO seamlessly handle it
https://arduino-esp8266.readthedocs.io/en/latest/installing.html#using-git-version

Let me figure out some remaining things though, and 3.2.0 would be published proper.

If git is out of the question... running build package .sh seems to produce some relevant files. I would guess package index .json should work in IDE
https://github.com/mcspr/esp8266-Arduino/releases/tag/3.2.0-dev
(but, idk if it actually works. open an issue there instead if it does not)

[ayushsharma82]

@mcspr For a layman, no, git install is too tedious. Surely we both can do it but most users won't unless strictly necessary. Most of the users are happy to use the board manager in Arduino IDE and PIO because it handles all the steps for them.

Also, tagged releases are important, this ensures the user that a specific tagged release is expected to work properly without critical bugs.

I know you guys have been actively merging PRs, all this can be done more efficiently within this repo. Take a look at appwrite’s repository and how they use Github projects to categorize issues and manage future releases. Ref: https://github.com/orgs/appwrite/projects/8/views/1?sliceBy%5Bvalue%5D=x.x.10