I’ve been reminded that there is a #networking discord…

Apologies for missing this email. What do people think about adding a dedicated discord channel (and potentially email list) to discuss network related items? Would be useful to triage the maxwell pro

It appears the github notification has changed where it now has the PR author as the person dismissing the stale reviews when pushing an update…

Update from GitHub support: GitHub Support (GitHub Support) Feb 23, 2022, 10:10 AM UTC Hi David, Thanks for reaching out to GitHub Support! Sorry for not getting back to you as quickly as we'd like! P

Just FYI, for reasons unknown, GitHub is attributing the dismissed approved reviews to my account, dleach02. I am not doing this and I have submitted a bug to the GitHub support to get them to look in

+1 on this response as it should be the first thing we attempt to do! In my past, my first instinct when getting these types of static analysis issues was to look at the underlying code to determine i

The networking and release management meetings now overlap… we should consider fixing that. David

Hi, We are excited to announce the release of Zephyr RTOS version 2.1.0! Major enhancements with this release include (but are not limited to): Normalized APIs across all architectures. Expanded suppo

Hi Zephyr developers, Zephyr 2.1.0-rc3 release candidate has been tagged. Current issue status: Priority Count Has PR High 0 - Medium 17 1 Testing Zephyr release candidate is requested; please, test t

The v2.1.0 release notes are lacking any updates for the following sections: Kernel Bluetooth Libraries/Subsystems HALs Documentation Tests and Samples Please help fill in these details. David David L

The problem has been addressed and the release candidate is now live. David Leach

There was a problem with how I attempted to create this release. In the process of fixing it and will send an update when ready. Sorry for any inconvenience. David Leach

Hi Zephyr developers, Zephyr 2.1.0-rc2 release candidate has been tagged. Current issue status: Priority Count Has PR High 0 - Medium 30 11 To get to an RC3 tag and eventual final release, we need get

Let me add a bit of emphasis. If you are working on a bug fix for a bug marked as “low priority” you should stop and move to one marked “medium” or “high” priority. We can pick up the low priority bug

The v2.1.0-rc1 is under test. The release schedule was to have a RC3 tagged by this weekend but we have not achieved RC2 level of quality yet. Current tradition is to have zero high priority bugs befo

Folks, As we get closer to completing release v2.1.0 we need the release notes updated with the major accomplishes and changes made to the various subsystems. Please start providing updates for us to

Hi Zephyr developers, Zephyr 2.1.0-rc1 release candidate has been tagged. All required features scheduled for 2.1 release are now merged into master. As of now we are in the stabilization phase for 2.

It looks like we need a PR to master to change doc/config.py to reference 1.14.1

For historical tracking, the error is because I have ZEPHYR_BASE environment variable set. Carles and I agree that the error message is not very helpful. David

Carles, See the following: dleach@dleach-test:~/work$ west init zephyrproject2 FATAL ERROR: already in an installation (/home/dleach/work/zephyrproject), aborting