-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Is a beta3 possible at this point? #5639
Comments
|
+1 |
On behalf of maintainers, we agreed. |
Is there any public timeline from the maintainers? |
@domingosl "within the next few days" |
Thx @d-a-v, appreciated - Closing this one for now as to not clutter the Issues page :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basic Infos
Platform
Settings in IDE
Problem Description
Question - Is it possible to do a beta3 release at this junction?
I'm using the Sonoff-Tasmota sketch and there are two major problems which have been addressed since the release of beta2.
The negative size issues on the linker files which prevents making binaries for 4M devices which were fixed with PR Fix negative SPIFFS size for 2M/4M (no SPIFFS) boards #5522
PWM which appears to be fixed by PR Make waveform generator a NMI to run always, increase accuracy #5578
We are actively encouraging the use of the 2.5.0 core for Sonoff-Tasmota builds but would like to use a released beta to be able to make it easier for users to easily test 2.5.0 in the hope that we can help in any way possible to iron out any potential bugs prior to the final release of 2.5.0. We also do pre-compiled binary releases for our development codebase and would like to use a (pre)released core to compile these as they are currently being automatically compiled using the beta2 release.
You guys do wonderful work and this is highly respected so I know it's not always possible to do what is being asked here due to time constraints but this is done in the spirit of trying to ensure that the 2.5.0 core is released with as minimal possible bugs (yes, we all want no bugs but it does not work like that in the real world :))
Thanks, much appreciated!
The text was updated successfully, but these errors were encountered: