1.0.0 rc.2 #73
Merged
1.0.0 rc.2 #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the next release candidate for 1.0.0, some major changes have been implemented. Read more about these changes below,
routing protocol now supports a proactive-style routing table management as was discussed in this issue thread, Alternative mesh routing protocol options #57 (comment). A detailed description of our implementation can be found on the wiki, https://github.com/sudomesh/disaster-radio/wiki/Protocol#routing
added the support for sending routed packets from a Console instance using
@symbol followed by the destination addressrestructured to allow portability between esp32 and simulator. All relevant firmware files are now contained within the
firmwaredirectory, including the disaster radiosrccode that is partially shared with the simulator.dropped support for ESP8266 as discussed in Support for legacy esp8266 WeMos dev boards #37
dropped support for makeEspArduino, it became too difficult to manage, platformio is much more accessible (though it is not perfect either).
added support for LoPy4, see Support FCC/ CE marked board #42