As some of you might already know: From now on ESPEasy binaries will be released automaticly every night, if there are any changes. This replaces the 'dev13..dev14..etc' numbering scheme and hopefully makes testing easier for everyone.
For the next upcoming 2.0.0 release (in bugfix-only mode since October 2017), use: https://github.com/letscontrolit/ESPEas ... 0-20180112
For the development version that has everything (including new bugs and features) use: https://github.com/letscontrolit/ESPEas ... a-20180112
Pending known issues for v2.0.0: https://github.com/letscontrolit/ESPEasy/milestone/1
Testing
TD-er and I have been fixing quite a lot of issues in the past few days, to finally get closer to the first stable v2.0.0 release.
There where a few showstoppers in v2.0 that we discovered quite late, so anyone that had lots of random reboots: please try these versions. Lack of testing is part of the reason we are seeing a lot of bugs and issues, that take long to fix.
One solution for this is to make it easier for people to test stuff, which is why we now release nightly builds. No need to compile things to test the latest fixes!
Automated testing
Testing always has been a problem with a big hardware project like ESPEasy. For example:
If we just want to test the ds18b12 temperature plugin, on both development branches, with all controllers, we would have to test 2 x 11 = 22 different combinations! Imagine if we want to test a large portion of the 70+ plugins we have against both branches and a few controllers.
So its impossible to test everything manually in a consistent way. Because of this reason i've been working on an automated testing framework and hardware rig. This means we can tests lots of hardware/controller-combinations automaticly and fix problems much quicker.
This week was the first time we used the testing frame work to quickly reproduce a bug, and quickly test if the bug was actually fixed.
Flash issues with ESP-01
Lots of people have flashing issues with this chip. Also see https://github.com/letscontrolit/ESPEasy/issues/650 .
We're waiting until the hardware is delivered so we can test this ourself.
Voting on issues
Since we're now having around 100 issues/feature requests, its important for people to tell us which ones are important to them. Use the thumps up feature on github to "vote" on the issues you think are important.
All issues, sorted by thumbs up count: https://github.com/letscontrolit/ESPEas ... -%2B1-desc
So it seems KRACK has number 1 priority. (we're waiting for platformio to get core 2.4.0).
After that is improved PWM support. Never would have known without the vote feature.
So start voting to let us know, otherwise we'll just fix random stuff we like ourself.
Slack and development
We've setup a slack for developers and testers that are actively contributing to ESPEasy. Its at https://espeasy.slack.com . I already invited a bunch of people (check your spamfolders
If you want to join contact us.I'm not checking the forum myself a lot, since there's simply too much information to process, i'm purely focused on the github issue tracker and development.
If you're absolutely sure you found a bug, use the issue tracker on github. We're only with a few devs so try to post only usefull information for development.
If you have some kind of problem, question, or idea for a new feature, use the forum. Lots of people can help you there, and the right people will point you to github if this is warranted.
I want to thank all the people that helped with development, testing, supporting and helping people on the forum and improving the wiki in the latest few weeks. You are great!