We are currently working to streamline the handling of bugs, questions and enhancements to improve the visibility and responses of topics raised for discussion. Previously all bugs, questions and enhancements have been collected as Github issues which is not optimal and our aim is to improve the handling of these topics with more appropriate tools.
This is the culmination of a lot of work over the past 18 months and we thought we’d use this as an opportunity to add a little background colour to today’s announcement.
Over the last couple of months we have been considering changing our Mbed OS release process. There are a number of reasons for this:
- We need to be able to release new functionality more frequently
- We need more flexibility to release features as they become mature (not released too early or delayed months before releasing)
- We would like to simplify our branching strategy
- It would allow us to improve the quality of our feature releases as they are not rushed to meet the current release cadence
- We need to be able to better support our Pelion Client release model
Arm TechCon (October 8-10, San Jose Convention Center) starts next week, if you’re planning to attend or in the California area, check out these sessions and talks featuring Arm and Mbed in IoT.
In the three years since we released Mbed OS 5, we’ve focused our engineering efforts on adding the feature set an IoT operating system requires. We’ve invested in connectivity, security, device management and storage. That investment has paid off. Mbed OS and Pelion Device Management now have most of the features required to develop, deploy and manage an IoT device.
In Mbed OS 5.14 we introduced a new directory structure convention and we started to clean-up the Mbed OS public headers.
You need to log in to post a reply