Thank you Nathan!
On 5/6/21, Nathan Hartman <hartman.nat...@gmail.com> wrote: > Summary: > +1 to release > > Verified: > * Signatures > * SHA-512 sums > * Incubating in artifact names > * LICENSE, NOTICE, README.md, DISCLAIMER-WIP present in both tarballs > * Build and run b-g474e-dpow1:nsh configuration successfully > * ReleaseNotes LGTM > > Notes and observations: > * apps/wireless/wapi contains a separate LICENSE file. I think this > should be moved into apps/LICENSE. I'll send a PR for review... > > Dependencies: > * gcc-arm-none-eabi-7-2017-q4-major: gcc version 7.2.1 20170904 > (release) [ARM/embedded-7-branch revision 255204] (GNU Tools for Arm > Embedded Processors 7-2017-q4-major) > * kconfig-conf from NuttX tools repository > > Other dependencies from Debian packages: > * binutils-dev: 2.31.1-16 > * bison: 2:3.3.2.dfsg-1 > * flex: 2.6.4-6.2 > * gperf: 3.1-1 > * libelf-dev: 0.176-1.1 > * libgmp-dev: 2:6.1.2+dfsg-4 > * libisl-dev: 0.20-2 > * libmpc-dev: 1.1.0-1 > * libmpfr-dev: 4.0.2-1 > * libncurses5-dev: 6.1+20181013-2+deb10u2 > * libusb-1.0-0-dev: 2:1.0.22-2 > * libusb-dev: 2:0.1.12-32 > * openocd: 0.10.0-5 > * texinfo: 6.5.0.dfsg.1-4+b1 > > Per Alan's request for size information: > > * NuttX-10.1.0-rc1, b-g474e-dpow1:nsh configuration: > > $ ls -l nuttx.bin > -rwxr-xr-x 1 test test 113912 Apr 19 12:40 nuttx.bin > > $ arm-none-eabi-size nuttx > text data bss dec hex filename > 113303 608 2612 116523 1c72b nuttx > > * For comparison, same configuration on NuttX-10.0.0: > > $ arm-none-eabi-size nuttx > text data bss dec hex filename > 116315 620 3008 119943 1d487 nuttx > > * Sizes have improved! From NuttX-10.0.0 to NuttX-10.1.0-rc0: > - text decreases by 3012 from 116315 to 113303 > - data decreases by 12 from 620 to 608 > - bss decreases by 396 from 3008 to 2612 > - total decreases by 3420 from 119943 to 116523 > > Development system: Linux (Debian 4.19.181-1 x86_64) > > Thanks to everyone for making this release (candidate) possible! > > Cheers, > Nathan > > On Thu, May 6, 2021 at 3:40 AM <alin.jerpe...@sony.com> wrote: >> >> Hi all, >> >> 72h have passed >> Can we get some votes to finish the 10.1 release? >> >> Thanks >> Alin >> >> >> -----Original Message----- >> From: alin.jerpe...@sony.com <alin.jerpe...@sony.com> >> Sent: den 3 maj 2021 17:17 >> To: dev@nuttx.apache.org >> Subject: RE: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release >> >> Hello all, >> >> This is the latest tarball >> >> I am sorry for the confusion >> >> Thanks >> Alin >> >> >> -----Original Message----- >> From: Nathan Hartman <hartman.nat...@gmail.com> >> Sent: den 3 maj 2021 17:14 >> To: dev@nuttx.apache.org >> Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release >> >> On Mon, May 3, 2021 at 1:22 AM Alin Jerpelea <jerpe...@gmail.com> wrote: >> > >> > Hello all, >> > Apache NuttX (Incubating) 10.1.0 RC1 has been staged under [1] and >> > it's time to vote on accepting it for release. If approved we will >> > seek final release approval from the IPMC. 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-10.1.0-RC1 >> > Hash for the release incubating-nuttx tag: >> > 3130ff691e386934eb276587a24d1efacf3bb30b >> > Hash for the release incubating-nuttx-apps tag: >> > 4348d91d1356335483089c3865282d80f13bedcd >> > >> > [1] >> > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc >> > ubator/nuttx/10.1.0-RC1/__;!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4 >> > HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBF0cM9oFQ$ >> > [2]https://urldefense.com/v3/__https://raw.githubusercontent.com/apach >> > e/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!u >> > 7bO_5TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBELDkRTXA$ >> > [3] >> > https://urldefense.com/v3/__https://www.apache.org/dev/release.html*ap >> > proving-a-release__;Iw!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4HI0T2 >> > TqnSm836Wse15R0SGxhUdWk3viAcBGKE_xsSw$ >> > [4]https://urldefense.com/v3/__https://cwiki.apache.org/confluence/dis >> > play/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!u7bO_5 >> > TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBE_QwknXQ$ >> >> >> Just to be sure I don't misunderstand, this is the latest release >> candidate to be tested now? >> >> In the future, I recommend to increment the -RC numbers each time there >> are new tarballs, to avoid any potential confusion. >> >> If this is indeed the latest RC, I'll try to test it today. >> >> Thanks for all your hard work!! >> >> Cheers, >> Nathan >
