Mbed Blog

Mbed OS 5.15. released today

We are pleased to announce the release of Mbed OS 5.15 today.

One of our primary focus areas over the past three months has been updating the underlying compiler infrastructure that we support in order to benefit from the performance optimizations and language enhancements those compilers bring to the Mbed ecosystem. Further, work continues to improve our support for Python 3 and many of our basic tools have been updated to support this version. For Mbed itself, we have added support in a backward compatible way for “static pin map tables” to further reduce memory consumption in scenarios where runtime modification is not needed and not required.

Continue reading »

The Mbed forums are changing

The Mbed ecosystem relies on its community to support others, identify bugs and share its experience. We want to help that community thrive and provide answers and help as quickly as possible. You've told us that the existing forum experience is confusing so to improve the community experience we're merging our various forums in to one at forums.mbed.com.

Continue reading »

Mbed OS 5.14.2 released

We are pleased to announce the Mbed OS 5.14.2 release is now available. This is the latest patch release based on the feature set that Arm Mbed OS 5.14 introduces.

Continue reading »

Check Out the Workshops and Register for the Arm AIoT Dev Summit Today!

https://os.mbed.com/media/uploads/gmetriArm/armaiotdevsummitlight.png

Attend the Arm AIoT Dev Summit on December 2nd-3rd and let’s change the landscape of AIoT, Together.

Continue reading »

Mbed OS 2020 release dates

As per our recent post: Change of Mbed OS release process, January 2020 will mark a change to how we make our releases for Mbed OS. This also has a knock on effect to our release dates. With this in mind we thought it would be useful to provide a list of actual code freeze and release dates:

Continue reading »

Arm AIoT Dev Summit: Mbed’s Top 5 Sessions to Attend

/media/uploads/gmetriArm/arm_aiot_twitter_banner_1500x500.png

The Arm AIoT Dev Summit will bring together developers, data scientists, technology experts and researchers to unleash the power of IoT and AI technologies. Taking place between 2nd and 3rd December at the Computer History Museum in Mountain View, California, the Dev Summit is set to focus on the present and future of AIoT and how, together, we can transform the technology landscape for the better.

We are excited to announce that the agenda has been published, showcasing the workshops, tech talks, focus groups, keynotes and Birds-of-a-Feather (BoF) sessions that you can benefit from. Read on to discover what to expect from the event and sessions you don’t want to miss as an Mbed developer.

Don’t forget to register and apply the special $75 ARMMBED discount code created for you, as this is a conference build for Mbed community.

Continue reading »

Improving the management of community input

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.

Continue reading »

Mbed OS 5.14.1 released

We are pleased to announce the Mbed OS 5.14.1 release is now available. This is the latest patch release based on the feature set that Arm Mbed OS 5.14 introduces.

Continue reading »

Introducing Partner Governance

Today we announced some changes we’ve made to how Mbed OS is governed.

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.

Continue reading »

Change of Mbed OS release process

Overview

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

Continue reading »

You need to log in to post a reply