There isn’t a list anywhere. Glad you started the list. I suggest at least 
capturing it on the Release roadmap page on cwiki. This will influence our 
decision on release schedule and version (major/minor):

https://cwiki.apache.org/confluence/display/MYNEWT/Release+Roadmap 
<https://cwiki.apache.org/confluence/display/MYNEWT/Release+Roadmap>

There is a PR sitting in the queue for sys/log where the updated log version 
would break backwards compatibility. 


> On Mar 19, 2018, at 3:21 PM, Simon Ratner <si...@proxy.co> wrote:
> 
> Is there a list of backwards-incompatible changes since 1.3.0 somewhere?
> 
> Things I am aware of:
> - adv data mbufs are now consumed by nimble
> - bsp code structure changes
> - nimble repo changes
> 
> But it is the things that I missed from the list/commit log that concern
> me, especially subtle semantic changes (like the first one above) that may
> not be picked up by the compiler.
> 
> Cheers,
> simon
> 
> 
> On Thu, Feb 8, 2018 at 12:50 PM, aditi hilbert <ad...@runtime.io> wrote:
> 
>> Martin,
>> 
>> Yes - that’s very cool! I see the PR is still open waiting for review.
>> Will get on the review and try-out.
>> 
>> thanks,
>> aditi
>> 
>> 
>>> On Feb 8, 2018, at 11:48 AM, Martin Turon <mtu...@google.com.INVALID>
>> wrote:
>>> 
>>> Aditi,
>>> 
>>> In addition to the FreeRTOS port, there is also a port of nimble over
>> Linux
>>> kernel.
>>> 
>>> Martin
>>> 
>>> _____________________________
>>> Martin Turon  |  Google
>>> 
>>> 
>>> On Wed, Feb 7, 2018 at 3:32 PM, aditi hilbert <ad...@runtime.io> 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
>>>> * NimBLE port to freeRTOS kernel
>>>> * 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
>> 
>> 

Reply via email to