Tracking Issue for version 0.1.0

[jonas-schievink]

0.1.0 milestone/issues

Rubble 0.1.0 is supposed to be a peripheral-side BLE stack that can be comfortably used for Hobby projects, trainings, and for general exploration. It should provide:

• A reliable Link-Layer with no known connection-breaking bugs (Don't give up when missing the initial transmit window #77 / LLCP updates are not applied when the event is missed #74)
• A sound implementation with no known memory safety bugs (tx_payload_buf problem #67)
• An ergonomic API for adding services and implementing custom ones (build.rs-based service declarations #72)
• Full support for all nRF52-series devices
• Examples showing how to use all major features, and full API docs

Out of scope for this release are:

• Pairing, Bonding, Encryption
• Power optimizations
• Full APIs for all conceivable Profiles
• Support for other chips (unless the nRF51 support somehow makes progress)
• Qualification of the stack
• Things that use Credit Based flow control L2CAP channels