Community Meeting Summary-[Sep 14 , 2023]

[Cathy-lulu]

Meeting Info
Date: Sep 14, 2023
Time: 8:00 PM(GMT+8)
Location: Online
Host: Meco
Attendance: RT-Thread Official Team & RT-Thread Community Committee Team
Meeting Type: Regular Community Meeting

Thanks for joining us at our latest community meeting! Here’s a summary of what we talked about:

1. Discuss PR issues [menuconfig] Add env file for fish #8026 [debug] rename RT_DEBUGING_INIT -> RT_DEBUGING_PRE_INIT #7920 [ci] add menuconfig check #7922.

2. Yangyang’s update: RT-Thread Pack on VSCode, we’re adding a button for online debugging and download functionality (optimizations will continue through PR submissions).

3. Meco: Addressing the ENV dist issue, there’s a --menuconfig error under dist that needs fixing (https://github.com/RT-Thread/rt-thread/issues/7918scons).

4. Sync-up for the 5.0.2 release, 5.0.2 is scheduled to release on September 30, 2023.

a. Error code discussion: The main goal is to resolve compatibility issues between RT error codes and POSIX error codes. (#7954). Achieved the consensus that RT error codes shouldn’t be restricted to kernel use only.
b. Kernel interruptable spelling error needs correction (rt_mb_recv_interruptibale).
c. The scons code that enforces a specific version needs to be removed. It was added because the new version had issues, but it’s no longer necessary.
d. RTC issue: It’s currently not user-friendly
–Xiao Quan has made some fixes, but we need to verify there are no remaining issues.
-ktimer: Consider whether to put it under components/drivers; use opts method callback instead of weak function.
e. Automatic initialization debug PR: #7920
f. Device driver v2 situation: Mao Sheng is working on the device tree documentation.
g. Maintenance of qemu aarch64/riscv64 RTOS and Smart versions – Jian Zhou’s task.
h. Transition from the coarse-grained lock to the fine-grained lock – planned for the next version, v5.0.3 | This PR needs to be ready before the version release so it can be quickly merged into the next version (#8042).
i. Considering adding functional features in the following version as we believe developers will be more interested in new features than only having the code details changes.

The next Community Meeting is scheduled for Sep 28. We hope to see you there!