+1 with caveat that I need to backport the compiler patch.

Toolchain:
clang version 13.0.0 (g...@github.com:jacobly0/llvm-project.git
ff3f5b865edbac826fdd251f810da833dda775de)
Target: ez80-none-unknown-elf
Thread model: posix

 - LICENSE, NOTICE, README.md, DISCLAIMER-WIP present in both repositories.
 - Build for eZ80 using commit ID 9d4742af00 backported from master, plus
patch for Z80 ELF support (PR to happen when tested adequately)
 - Build size is 253,610 text (down from 257,713 bytes for RC0), 197 bytes
in data (unchanged from RC0)

NuttShell (NSH) NuttX-10.1.0
nsh> free
                     total       used       free    largest
        Umem:       253856      66272     187584     184736

-- 
bje

On Tue, May 4, 2021 at 1:25 AM Alan Carvalho de Assis <acas...@gmail.com>
wrote:

> Hi Everyone, please submit some information when you test it:
>
> - Used toolchain: i.e. last line of "gcc -v" is enough
> - ELF nuttx size: i.e. "arm-none-eabi-size nuttx"
> - Result of internal nsh free command.
>
> It will help us to track the size increase from a release to another.
>
> BR,
>
> Alan
>
> On 5/3/21, alin.jerpe...@sony.com <alin.jerpe...@sony.com> wrote:
> > 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
> >
>

Reply via email to