Hi, On Thu, Feb 8, 2018 at 12:32 AM, aditi hilbert <[email protected]> wrote:
> Hi all, > > There has been a lot of feature additions and bug fixes since our last > release on Dec 13, 2018. > I’d like to propose we try to get a release out in two weeks (Feb 21st). > Below are some of the things we have added: > > * Fixes for NimBLE 5 and Mesh issues found at upf59 last week > * Fixes for NimBLE 5 issues found during BT certification testing > Also we'll have support for advertising data fragmentation (i.e. AUX_CHAIN_IND) which was successfully tested on UPF59 and hopefully will be merged soon: https://github.com/apache/mynewt-core/pull/770 > * NimBLE port to freeRTOS kernel > This is actually being worked on in separate repository (mynewt-nimble) so we now have two separate repositories with Nimble code. The goal is to have mynewt-nimble as the only repository with Nimble code and build Mynewt with that code. I think it would make sense to aim for completing this split after current release so we can develop Nimble in one place and also start raising issues on GitHub for proper repository. If this makes sense, I can send separate e-mail for discussion later. > * LoRa enhancements (e.g. config variable to distinguish boards with and > without antenna switch) > * Support for additional hardware: Cortex M3 (STM32L152), ARCv2 > architecture > * Update supported tools e.g. STM32Cube > * Additional sensor support: DRV2605L haptic driver for LRA and ERM > * Port of image manager to other non-Mynewt OS > * Newt tool bug fixes and minor features > > This means we get a release candidate out next week. Can we get one out by > Feb 15th? > > thanks, > Aditi Best regards, Andrzej
