My replies with IPG>> prefixed below

Thanks for the summary, Anas >> 4. We are considering a new communication platform to replace IRC. Candidates are Slack and gitter. This has not been decided yet, if you have any feedback, please let

From: zephyr-devel-bounces@... [zephyr-devel-bounces@...] on behalf of Boie, Andrew P [andrew.p.boie@...] Sent: Wednesday, May 24, 2017 12:01 PM To: Zephy

I see it too Please file a bug and assign to David Kinder -- he can do more research on it.

Intel's ISSM might provide what you are looking for. (obvious disclaimer: I work for Intel)

I haven't been able to test ipv6 on the automation framework yet, but if past experience is to be heeded, I would not be surprised if lurking issues were there. _______________________________________

Hello All Please consider https://gerrit.zephyrproject.org/r/5355; it has been brought to our attention that the way we distribute kbuild and kconfig makes it look like it is Apache license, where it

Hello All New RC tagged. Thank you for your contributions-we are getting closer to a release, with 48 new fixes Please remember for rc3 to keep it only for fixes; please consider: - If your commit can

Hello All New RC tagged. Thank you for your contributions For the next cycle in the upcoming week, let's aim at trying to reduce the amount patches to more strictly necessary with a reduced size; plea

Sent: Friday, August 5, 2016 5:51 AM To: Perez-Gonzalez, Inaky <inaky.perez-gonzalez(a)intel.com>; devel(a)lists.zephyrproject.org Subject: RE: About the testing framework Hi, Guess our targest are pa

Hi Jaakko A few weeks ago I presented in the TSC an automated testing solution we are now in the process of opensourcing so the project as a whole can use it. It is the opposite of unit testing, as it

Hello All Please remember we'll tag v1.5.0-rc1 end of day Friday (PDT Time Zone) We are in code freeze, so to make processing swifter for everyone, please state in contributions what is being fixed by

Thank you for your contributions, everyone! Please, only bug fixes, documentation updates and test case updates from now on rc1 due on Friday Aug 5th EOD PDT.

I think it calls for a separate include I'd put public app interfaces in include/zephyr anything in include/ itself is a private kernel interface, fair game (same applies to include/subarea) _________

rc0 will be then released, rc1 next Friday Thank you!

Are there any in-kernel users? ________________________________ Sent: Friday, July 29, 2016 1:28 AM To: devel(a)lists.zephyrproject.org Subject: [devel] deprecation policy Do we have a concrete policy

Hello All Please be aware that the merge window will be closing on Aug 1st / 2nd (a wee fuzzy as I am traveling on different time zones). - First rc0 will be tagged on around Aug 3rd. RCs will be rele

Thanks for all the feedback -- it definitely looks that it is staying as people very actively rely on it, so I'll close the ticket but first I'll add the feedback to it for future reference in case an

Certainly, ZEPHYR_BASE is tree-specific (so could be the other in certain cases, but uncommon). I also do set it manually (in fact, as I said somewhere, I feed it to make's command line) This is the o

to avoid those issues I usually run make ZEPHYR_BASE=DIR <blah>, which is kind of more verbose, but gets the trick done. However, I hear your call. I think it's worthwhile to consider the posibility o