Skip to content
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

Closed
4 of 6 tasks
andrethomas opened this issue Jan 19, 2019 · 6 comments
Closed
4 of 6 tasks

Is a beta3 possible at this point? #5639

andrethomas opened this issue Jan 19, 2019 · 6 comments

Comments

@andrethomas
Copy link

Basic Infos

  • This issue complies with the issue POLICY doc.
  • I have read the documentation at readthedocs and the issue is not addressed there.
  • I have tested that the issue is present in current master branch (aka latest git).
  • I have searched the issue tracker for a similar issue.
  • If there is a stack dump, I have decoded it.
  • I have filled out all fields below.

Platform

  • Hardware: [ESP-12]
  • Core Version: [bd11d02]
  • Development Env: [Arduino IDE]
  • Operating System: [Windows]

Settings in IDE

  • Module: [Generic ESP8266 Module]
  • Flash Mode: [dout]
  • Flash Size: [4MB]
  • lwip Variant: [v2 Lower Memory]
  • Reset Method: [ck]
  • Flash Frequency: [40Mhz]
  • CPU Frequency: [80Mhz]
  • Upload Using: [OTA]
  • Upload Speed: [] (serial upload only)

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.

  1. 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

  2. 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!

@Jason2866
Copy link
Contributor

Jason2866 commented Jan 19, 2019

+ 1

@domingosl
Copy link

+1

@d-a-v
Copy link
Collaborator

d-a-v commented Jan 19, 2019

in the spirit of trying to ensure that the 2.5.0 core is released with as minimal possible bugs

On behalf of maintainers, we agreed.
It will probably happen within the next few days.

@domingosl
Copy link

Is there any public timeline from the maintainers?

@andrethomas
Copy link
Author

@domingosl "within the next few days"

@andrethomas
Copy link
Author

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants