Re: release branches strings and notes :-)
On Fri, 30 Jun 2023, 16:35 Tomek CEDRO, wrote: > On Fri, Jun 30, 2023 at 3:18 PM Alin Jerpelea wrote: > > On Fri, 30 Jun 2023, 16:13 Tomek CEDRO, wrote: > > > * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it > > > is 12.2.0 in the console and 12.2 in the git branch usually RC also > > > have their own branch)? > > > > the rc release after aproval becomes the release without repackinf > > Yes, but its not yet 12.2.0 release, so 12.2.0-RC0 is the only valid > name here :-) > there are the release tags for the release while the lelease/xx.xx can be considered the release work branch > > > * Note: Can we use name branches releases/12.2.0 (currently > > > releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) > > > > the release/number is thw main branch from which the tags xx.xx.xx are > > generated. on a lomg term having multiple branches for each major and > minor > > release will be hard to scale and navigate. > > 12.2 is not the same as 12.2.0 o_O > > It is hard to navigate right now because I am looking for 12.2.0 and > its not there.. the same with 12.2.0-RC0 :-) > > Please lets keep things coherent :) please use the release tags > > * General Question: Is it possible to reverse ReleaseNotes sorting > > > order so the latest release notes are on top (not bottom) of the file? > > > :-) > > > > > > * Note: ReleaseNotes should keep formatting of a release header > > > (NuttX-12.2.0\n---). > > > > after this release I am planing to propose moving the release notes to a > > separate folder and create a release note file for each release > > Good idea thanks Alin! :-) > > > Best regards! :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: release branches strings and notes :-)
On Fri, Jun 30, 2023 at 3:18 PM Alin Jerpelea wrote: > On Fri, 30 Jun 2023, 16:13 Tomek CEDRO, wrote: > > * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it > > is 12.2.0 in the console and 12.2 in the git branch usually RC also > > have their own branch)? > > the rc release after aproval becomes the release without repackinf Yes, but its not yet 12.2.0 release, so 12.2.0-RC0 is the only valid name here :-) > > * Note: Can we use name branches releases/12.2.0 (currently > > releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) > > the release/number is thw main branch from which the tags xx.xx.xx are > generated. on a lomg term having multiple branches for each major and minor > release will be hard to scale and navigate. 12.2 is not the same as 12.2.0 o_O It is hard to navigate right now because I am looking for 12.2.0 and its not there.. the same with 12.2.0-RC0 :-) Please lets keep things coherent :-) > * General Question: Is it possible to reverse ReleaseNotes sorting > > order so the latest release notes are on top (not bottom) of the file? > > :-) > > > > * Note: ReleaseNotes should keep formatting of a release header > > (NuttX-12.2.0\n---). > > after this release I am planing to propose moving the release notes to a > separate folder and create a release note file for each release Good idea thanks Alin! :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: ESP32 question
On Fri, Jun 30, 2023 at 7:53 AM Milan Obuch wrote: > Problem here is not using additional USB/serial cable, I do it > regularly if necessary or useful, but pins for UART0 (GPIOs 43 and 44) > are not available on any pin, thus my attempt to use UART1. GPIOs 17 > and 18 are accessible on this board, is it not possible to use them for > console? Hey there Milan :-) I just tested 12.2.0-RC0 on ESP32S2 WEMOS S2 Mini and Pico boards.. I had to update UART pins in the config so use console over external UART-to-USB converter. ./tools/configure.sh -B esp32s2-saola-1:coremark You may want to use :nsh defconfig :-) Then: kconfig-tweak --set-val CONFIG_ESP32S2_UART0_TXPIN 2 kconfig-tweak --set-val CONFIG_ESP32S2_UART0_RXPIN 3 gmake olddefconfig Then: gmake -j8 gmake flash In order to flash keep Button 0 pressed while RST then MCU will switch into a Bootloader mode via USB-C connection. After flash press RST and you should have console on selected pins :-) I am working on a priority project right now, after its done I will add board configurations for WEMOS boards that we have (you can try that yourself its a good learning path) and some BSD build related fixes (i.e. you need to change sed to gsed in some places). Have fun! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: release branches strings and notes :-)
On Fri, 30 Jun 2023, 16:13 Tomek CEDRO, wrote: > Hello world :-) > > On 12.2.0-RC0 I noticed some stuff that it may be good to discuss :-) > > * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it > is 12.2.0 in the console and 12.2 in the git branch usually RC also > have their own branch)? > the rc release after aproval becomes the release without repackinf > > * Note: Can we use name branches releases/12.2.0 (currently > releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) > the release/number is thw main branch from which the tags xx.xx.xx are generated. on a lomg term having multiple branches for each major and minor release will be hard to scale and navigate. * General Question: Is it possible to reverse ReleaseNotes sorting > order so the latest release notes are on top (not bottom) of the file? > :-) > > * Note: ReleaseNotes should keep formatting of a release header > (NuttX-12.2.0\n---). > after this release I am planing to propose moving the release notes to a separate folder and create a release note file for each release > Thanks! :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: ESP32 question
Hi Milan, On 6/30/23, Milan Obuch wrote: > On Thu, 29 Jun 2023 19:29:39 -0300 > "Alan C. Assis" wrote: > >> Hi Milan, >> >> This S2-Mini board powered by ESP32-S2 seems to use the USB Controller >> directed instead of using an external USB/Serial chip like the other >> boards you cited. >> >> Also keep in mind that ESP32-S2 chip doesn't have internally the >> USB_SERIAL_JTAG Controller that exist on ESP32-C3 and ESP32-S3 chips >> and are pretty ease to add support. >> >> So to get the Console working on ESP32-S2 you have two options: >> >> 1) Connect a USB/Serial adapter directly the the pins used as UART0, >> not ideal because probably you don't want attachment like it to your >> board; > > Problem here is not using additional USB/serial cable, I do it > regularly if necessary or useful, but pins for UART0 (GPIOs 43 and 44) > are not available on any pin, thus my attempt to use UART1. GPIOs 17 > and 18 are accessible on this board, is it not possible to use them for > console? > I think you spot an issue in our Kconfig, by default UART1 TXD and RXD should be 17 and 18, but it was 37 and 38. So, if you apply this patch: diff --git a/boards/xtensa/esp32s2/esp32s2-saola-1/configs/nsh/defconfig b/boards/xtensa/esp32s2/esp32s2-saola-1/configs/nsh/defconfig index 9465c7706a..92f0a8dad1 100644 --- a/boards/xtensa/esp32s2/esp32s2-saola-1/configs/nsh/defconfig +++ b/boards/xtensa/esp32s2/esp32s2-saola-1/configs/nsh/defconfig @@ -19,7 +19,9 @@ CONFIG_ARCH_STACKDUMP=y CONFIG_ARCH_XTENSA=y CONFIG_BOARD_LOOPSPERMSEC=16717 CONFIG_BUILTIN=y -CONFIG_ESP32S2_UART0=y +CONFIG_ESP32S2_UART1=y +CONFIG_ESP32S2_UART1_RXPIN=18 +CONFIG_ESP32S2_UART1_TXPIN=17 CONFIG_FS_PROCFS=y CONFIG_HAVE_CXX=y CONFIG_HAVE_CXXINITIALIZE=y @@ -41,4 +43,4 @@ CONFIG_START_MONTH=12 CONFIG_START_YEAR=2011 CONFIG_SYSLOG_BUFFER=y CONFIG_SYSTEM_NSH=y -CONFIG_UART0_SERIAL_CONSOLE=y +CONFIG_UART1_SERIAL_CONSOLE=y Compile: $ make distclean $ ./tools/configure.sh esp32s2-saola-1:nsh $ make -j Flash the nuttx.bin in your board at position 0x1 to skip bootloader anf partitions. Then using a USB/Serial adapter in the pins 17 and 18 and you will see the terminal: NuttShell (NSH) NuttX-12.1.0 nsh> uname -a NuttX 12.1.0 9603288c80-dirty Jun 30 2023 10:03:48 xtensa esp32s2-saola-1 >> 2) add support to USB Device on ESP32-S2, fortunately there is a port >> done for ESP32-S3 and that could be used as base, because the USB >> Controller is basically the same with only some differences related >> pins, clock initialization, etc. Probably looking how it is done on >> IDF you will get it working. > > Should I take it as there is no USB support for ESP-S2 at the moment? > From ESP32-S3, which files are to be ported? I am not sure I can do it > myself as I am only starting to learn Espressif devices... and, to be > honest, I am still learning basics of NuttX as well. > This file: arch/xtensa/src/esp32s3/esp32s3_otg_device.c You can see the patch here: https://github.com/apache/nuttx/pull/9525 BR, Alan
release branches strings and notes :-)
Hello world :-) On 12.2.0-RC0 I noticed some stuff that it may be good to discuss :-) * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it is 12.2.0 in the console and 12.2 in the git branch usually RC also have their own branch)? * Note: Can we use name branches releases/12.2.0 (currently releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) * General Question: Is it possible to reverse ReleaseNotes sorting order so the latest release notes are on top (not bottom) of the file? :-) * Note: ReleaseNotes should keep formatting of a release header (NuttX-12.2.0\n---). Thanks! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [VOTE] Apache NuttX 12.2.0 RC0 release
Let's move the topics to a dev thread Best Regards Alin On Fri, 30 Jun 2023, 16:00 Tomek CEDRO, wrote: > On Fri, Jun 30, 2023 at 10:48 AM Alin Jerpelea wrote: > > Hello all, > > Apache NuttX 12.2.0 RC0 has been staged under [1] and it's time to vote > on > > accepting it for release. Voting will be open for 72hr. > > Hello world :-) > > +1 here on ESP32 / ESP32-C3 / ESP32-S2 :-) > > > Remarks: > * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it > is 12.2.0 in the console and 12.2 in the git branch usually RC also > have their own branch)? > * Note: Can we use name branches releases/12.2.0 (currently > releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) > * General Question: Is it possible to reverse ReleaseNotes sorting > order so the latest release notes are on top not bottom of the file? > :-) > * Note: ReleaseNotes should keep formatting of a release header > (NuttX-12.2.0\n---). > > > > Tested on FreeBSD 13.2-RELEASE AMD64: > > % uname -a > FreeBSD octagon 13.2-RELEASE FreeBSD 13.2-RELEASE > releng/13.2-n254617-525ecfdad597 GENERIC amd64 > > > > Build targets: > > 1. ESP32 / esp32-devkitc:ostest. > > NuttShell (NSH) NuttX-12.2.0 > nsh> uname -a > NuttX 12.2.0 26f5e973f6 Jun 30 2023 13:08:31 xtensa esp32-devkitc > > % xtensa-esp32-elf-gcc -v > Using built-in specs. > COLLECT_GCC=xtensa-esp32-elf-gcc > > COLLECT_LTO_WRAPPER=/usr/home/XXX/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch5-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper > Target: xtensa-esp32-elf > Configured with: > /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure > --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu > --target=xtensa-esp32-elf > --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf > --exec_prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf > > --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf > > --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include > --with-newlib --enable-threads=no --disable-shared > --with-pkgversion='crosstool-NG esp-2021r2-patch5' > --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections > --disable-libgomp --disable-libmudflap --disable-libmpx > --disable-libssp --disable-libquadmath --disable-libquadmath-support > --disable-libstdcxx-verbose > --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --enable-lto --enable-target-optspace --without-long-double-128 > --disable-nls --enable-multiarch --enable-languages=c,c++ > --disable-libstdcxx-verbose --enable-threads=posix > --enable-gcov-custom-rtio --enable-libstdcxx-time=yes > Thread model: posix > gcc version 8.4.0 (crosstool-NG esp-2021r2-patch5) > > % /usr/bin/time -h gmake clean distclean > 7,64s real 3,72s user 4,03s sys > > % /usr/bin/time -h ./tools/configure.sh -B esp32-devkitc:ostest > 2,97s real 1,64s user 1,37s sys > > % /usr/bin/time -h gmake -j8 > 16,70s real 57,00s user 37,95s sys > > > > > 2. ESP32-C3 / esp32c3-devkit:usbconsole. > > NuttShell (NSH) NuttX-12.2.0 > nsh> uname -a > NuttX 12.2.0 26f5e973f6 Jun 30 2023 13:47:22 risc-v esp32c3-devkit > > % riscv64-none-elf-gcc -v > Using built-in specs. > COLLECT_GCC=riscv64-none-elf-gcc > > COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/riscv64-none-elf/11.3.0/lto-wrapper > Target: riscv64-none-elf > Configured with: > /wrkdirs/usr/ports/devel/riscv64-none-elf-gcc/work/gcc-11.3.0/configure > --target=riscv64-none-elf --disable-nls --enable-languages=c,c++ > --enable-gnu-indirect-function --without-headers --with-gmp=/usr/local > --with-pkgversion='FreeBSD Ports Collection for riscv64noneelf' > --with-system-zlib --with-gxx-include-dir=/usr/include/c++/v1/ > --with-sysroot=/ --with-as=/usr/local/bin/riscv64-none-elf-as > --with-ld=/usr/local/bin/riscv64-none-elf-ld --prefix=/usr/local > --localstatedir=/var --mandir=/usr/local/man > --infodir=/usr/local/share/info/ --build=x86_64-unknown-freebsd13.1 > Thread model: single > Supported LTO compression algorithms: zlib > gcc version 11.3.0 (FreeBSD Ports Collection for riscv64noneelf) > > % /usr/bin/time -h gmake clean distclean > 7,64s real 3,76s user 3,99s sys > > % /usr/bin/time -h ./tools/configure.sh -B esp32c3-devkit:usbconsole > 2,97s real 1,54s user 1,46s sys > > % /usr/bin/time -h gmake -j8 CROSSDEV=riscv64-none-elf- > 26,81s real 2m19,76s user 29,04s sys > > > 3. ESP32-S2 / esp32s2-saola-1:coremark. > > CoreMark 1.0 : 468.384075 / GCC8.4.0 -O3 -fno-strict-aliasing > -fomit-frame-pointer -ffunction-sections
Re: [VOTE] Apache NuttX 12.2.0 RC0 release
On Fri, Jun 30, 2023 at 10:48 AM Alin Jerpelea wrote: > Hello all, > Apache NuttX 12.2.0 RC0 has been staged under [1] and it's time to vote on > accepting it for release. Voting will be open for 72hr. Hello world :-) +1 here on ESP32 / ESP32-C3 / ESP32-S2 :-) Remarks: * Question: Shouldn't 12.2.0-RC0 contain 12.2.0-RC0 version string (it is 12.2.0 in the console and 12.2 in the git branch usually RC also have their own branch)? * Note: Can we use name branches releases/12.2.0 (currently releases/12.2) as "12.2.0" != "12.2" plus remark on RC above :-) * General Question: Is it possible to reverse ReleaseNotes sorting order so the latest release notes are on top not bottom of the file? :-) * Note: ReleaseNotes should keep formatting of a release header (NuttX-12.2.0\n---). Tested on FreeBSD 13.2-RELEASE AMD64: % uname -a FreeBSD octagon 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64 Build targets: 1. ESP32 / esp32-devkitc:ostest. NuttShell (NSH) NuttX-12.2.0 nsh> uname -a NuttX 12.2.0 26f5e973f6 Jun 30 2023 13:08:31 xtensa esp32-devkitc % xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc COLLECT_LTO_WRAPPER=/usr/home/XXX/.espressif/tools/xtensa-esp32-elf/esp-2021r2-patch5-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper Target: xtensa-esp32-elf Configured with: /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --exec_prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG esp-2021r2-patch5' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --disable-libstdcxx-verbose --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2-patch5) % /usr/bin/time -h gmake clean distclean 7,64s real 3,72s user 4,03s sys % /usr/bin/time -h ./tools/configure.sh -B esp32-devkitc:ostest 2,97s real 1,64s user 1,37s sys % /usr/bin/time -h gmake -j8 16,70s real 57,00s user 37,95s sys 2. ESP32-C3 / esp32c3-devkit:usbconsole. NuttShell (NSH) NuttX-12.2.0 nsh> uname -a NuttX 12.2.0 26f5e973f6 Jun 30 2023 13:47:22 risc-v esp32c3-devkit % riscv64-none-elf-gcc -v Using built-in specs. COLLECT_GCC=riscv64-none-elf-gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/riscv64-none-elf/11.3.0/lto-wrapper Target: riscv64-none-elf Configured with: /wrkdirs/usr/ports/devel/riscv64-none-elf-gcc/work/gcc-11.3.0/configure --target=riscv64-none-elf --disable-nls --enable-languages=c,c++ --enable-gnu-indirect-function --without-headers --with-gmp=/usr/local --with-pkgversion='FreeBSD Ports Collection for riscv64noneelf' --with-system-zlib --with-gxx-include-dir=/usr/include/c++/v1/ --with-sysroot=/ --with-as=/usr/local/bin/riscv64-none-elf-as --with-ld=/usr/local/bin/riscv64-none-elf-ld --prefix=/usr/local --localstatedir=/var --mandir=/usr/local/man --infodir=/usr/local/share/info/ --build=x86_64-unknown-freebsd13.1 Thread model: single Supported LTO compression algorithms: zlib gcc version 11.3.0 (FreeBSD Ports Collection for riscv64noneelf) % /usr/bin/time -h gmake clean distclean 7,64s real 3,76s user 3,99s sys % /usr/bin/time -h ./tools/configure.sh -B esp32c3-devkit:usbconsole 2,97s real 1,54s user 1,46s sys % /usr/bin/time -h gmake -j8 CROSSDEV=riscv64-none-elf- 26,81s real 2m19,76s user 29,04s sys 3. ESP32-S2 / esp32s2-saola-1:coremark. CoreMark 1.0 : 468.384075 / GCC8.4.0 -O3 -fno-strict-aliasing -fomit-frame-pointer -ffunction-sections -fdata-sections / Stack Running CoreMark... 2K performance run parameters for coremark. CoreMark Size: 666 Total ticks : 12810 Total time (secs): 12.81 Iterations/Sec : 468.384075 Iterations : 6000 Compiler version : GCC8.4.0 Compiler flags : -O3 -fno-strict-aliasing -fomit-frame-pointer -ffunction-sections
Re: [VOTE] Apache NuttX 12.2.0 RC0 release
+1 for PinePhone = Compiler + aarch64-none-elf-gcc -v Using built-in specs. COLLECT_GCC=aarch64-none-elf-gcc COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper Target: aarch64-none-elf Configured with: /Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure --target=aarch64-none-elf --prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install --with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --disable-shared --disable-nls --disable-threads --disable-tls --enable-checking=release --enable-languages=c,c++,fortran --with-newlib --with-gnu-as --with-gnu-ld --with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf --with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl= https://bugs.linaro.org/ Thread model: single Supported LTO compression algorithms: zlib gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1) = Configuration + ./tools/configure.sh pinephone:nsh = Size + aarch64-none-elf-size nuttx text databssdechex filename 221412 12921 41615 275948 435ec nuttx = NSH Info and Free NuttShell (NSH) NuttX-12.2.0 nsh> uname -a NuttX 12.2.0 26f5e973f6 Jun 30 2023 18:41:32 arm64 pinephone nsh> free total used freelargest nused nfree Umem: 133410808 551480 132859328 132859232 58 2 Complete Log: https://gist.github.com/lupyuen/3b6f7ab19e687e5d9ca57b85df36de2a Validation Script: https://gist.github.com/lupyuen/73bab36c5d9fa0ccd94fefe8ea1a7195 Lup On Fri, Jun 30, 2023 at 4:48 PM Alin Jerpelea wrote: > Hello all, > > Apache NuttX 12.2.0 RC0 has been staged under [1] and it's time to vote on > accepting it for release. Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 are > required to pass. > > > > The Apache requirements for approving a release can be found here [3] > "Before voting +1 [P]PMC members are required to download the signed source > code package, compile it as provided, and test the resulting executable on > their own platform, along with also verifying that the package meets the > requirements of the ASF policy on releases." > > > > A document to walk through some of this process has been published on our > project wiki and can be found here [4]. > > > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM > items in [4]) > > [ ] -1 reject (explanation required) > > > > Thank you all, > > Alin Jerpelea > > > > SCM Information: > > Release tag: nuttx-12.2.0-RC0 > > Hash for the release nuttx tag: 26f5e973f68a7bb4ee66915fce2c723641d5e045 > > Hash for the release nuttx-apps tag: > 86efbcbee77bc0a29af07807080f4804a37f46a3 > > > [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.0-RC0/ > [2] > https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.0-RC0/ReleaseNotes > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] > https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release >
[VOTE] Apache NuttX 12.2.0 RC0 release
Hello all, Apache NuttX 12.2.0 RC0 has been staged under [1] and it's time to vote on accepting it for release. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. The Apache requirements for approving a release can be found here [3] "Before voting +1 [P]PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." A document to walk through some of this process has been published on our project wiki and can be found here [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) Thank you all, Alin Jerpelea SCM Information: Release tag: nuttx-12.2.0-RC0 Hash for the release nuttx tag: 26f5e973f68a7bb4ee66915fce2c723641d5e045 Hash for the release nuttx-apps tag: 86efbcbee77bc0a29af07807080f4804a37f46a3 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.0-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.0-RC0/ReleaseNotes [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
