Thank you Stephanos. Great work and a huge thank you to all the contributors, maintainers and release engineers who made this happen. Anas From: devel@... <devel@...

Hi, Below is the agenda for tomorrow’s API meeting: Sensor API update (https://github.com/zephyrproject-rtos/zephyr/pull/44098) Yuval Peress RFC: API Change: Bluetooth - replace callback in bt_gatt_su

Hit send too fast… fixed subject. From: Nashif, Anas <anas.nashif@...> Date: Friday, February 11, 2022 at 9:40 AM To: devel@... <devel@...> Subject: Chang

Hi, The TSC has discussed and voted in favor of changing the pull request and review process by enabling options provided by Github. Specifically, we will be enabling an option that will cause new rev

Hi, I suggest reviewing this document which will be discussed in the TSC this week: https://docs.google.com/document/d/1heqcv7dzGvM5rA9xpTMW3kyKJLpZsl2Gjsmr5eqBje8/edit Look at the “Allowed types” sec

Olof, Point taken, will start posting agenda the day before. Anas From: devel@... <devel@...> on behalf of Olof Johansson <olof@...> Date: Wednesday, Dece

Hi Nicolas, Just a note that the project is not seeking MISRA compliance, we only looking at complying with our own published coding guidelines (which is a subset of MISRA). When we adopted the coding

Hello again, I wanted to clarify that this call for help is targeted at everyone who is currently an active contributor to the project (collaborator, maintainer, etc.) and not limited to contributors

Hello Everyone, We are slowly approaching the 6th anniversary since the project was launched and the community continues to grow nicely. We have been coping well with the growth until now, however, we

Hello Everyone, We have done some changes to the project CI and switched to Github action for the main workflow running twister. This workflow was run using buildkite until now. The change requires a

Oops, sorry about the bad formatting, the correct link is https://github.com/zephyrproject-rtos/zephyr/discussions/39437 Anas On 2021-10-18, 4:36 PM, "devel@... on behalf of Nashi

Hello, The changes below will take effect today. If you are a Zephyr project collaborator or maintainer and notice that your access was downgraded, then make sure your github name is in the MAINTAINER

Hello everyone, We recently made changes to the project roles and the access levels given to contributors on github. Please refer to the full documentation of the roles below for more details: https:/

Conor, Thank you for sharing, this is great. Just a quick comment, from a quick look at the links below, I noticed the arch changes to riscv adding smp support and other generic code references your S

Hi, Here is a TOP10 list to improve and accelerate the review process of pull requests. If you follow them, chances are your pull request will get the attention needed and it will be ready for merge s

Hi Roberto, I will connect with you shortly. Sorry about the delay, been a busy weel. Anas On 02/03/2021, 09:02, "tsc@... on behalf of Roberto Bagnara" <tsc@...

Hi, There is nothing absurd about discussing this topic at any time. This is a major release with significant impact, and we should be able to make the assessment and have a judgment call if we are re

Hi, We are pleased to announce the release of Zephyr RTOS version 2.5.0! Major enhancements with this release include: Introduced support for the SPARC processor architecture and the LEON processor im

Hi, The fourth release candidate for Zephyr v2.5.0 has been tagged (v2.5.0-rc4). This is planned to be the last release candidate. Only blocker issues will be considered. The merge window for features

Hi, The third release candidate for Zephyr v2.5.0 has been tagged (v2.5.0-rc3). The merge window for features and enhancements remains closed until v2.5.0 is released. The next release milestone is co