Re: What gets patched onto previous releases?

[Alin Jerpelea]

I think that we should consider making the last release from a series an
LTS release and patch that one for a decided period (ex 12 months)
This way a downstream project that uses an older release can always use the
latest release that is API compatible without the need to patch the project.

If you need help with the patches and release I offer to help

//Alin

On Fri, 18 Sep 2020, 16:06 Gregory Nutt,  wrote:

>
> > I completely understand that it takes work to patch and regression test
> > previous releases, but I just want to understand our policy and threshold
> > for what gets backported.
>
> There should be an established policy.  I agree on that.
>
> In the old BDFL model, I only updated releases via patches and only for
> about two weeks after the release.  The only purpose being to assure
> that the release was a valid stable snapshot of the development.  After
> that, well then the release just has bugs.
>
>  From Brennan's response, it seems like we are limited in the same way,
> not by policy but by process.
>
> But perhaps we should consider an LTS release?  Perhaps the last in
> series of releases with the same major revision number should be an LTS
> release?
>
>

Re: NuttX-10.1

[Alin Jerpelea]

I would like to wait until 1st April so that most licensed are cleared to
Apache
then I would like to help as a release managed

Regards
Alin

On Fri, Mar 19, 2021 at 8:46 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:

> Hi,
>
> Our latest release was on December 6th.  It's fair to say that we
> should start planning for NuttX-10.1.
>
> Last time Adam and Alin offered to be release managers, do you guys
> still want to do that?
>
> We can start by devising our plan and pick a date to create the branches.
>

Re: NuttX-10.1

[Alin Jerpelea]

Hi Abdelaif,

I think that we are in a better position now form a license perspective and
I can take the role as release manager for 10.1


Can you please point me to the checklist for the release

Best regards
Alin


On Fri, Mar 19, 2021 at 8:46 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:

> Hi,
>
> Our latest release was on December 6th.  It's fair to say that we
> should start planning for NuttX-10.1.
>
> Last time Adam and Alin offered to be release managers, do you guys
> still want to do that?
>
> We can start by devising our plan and pick a date to create the branches.
>

Re: NuttX-10.1

[Alin Jerpelea]

Thanks Abdelatif,

I will dig into it and call for a branch ASAP

Thanks
Alin


On Thu, Apr 1, 2021, 22:40 Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:

> Hi Alin,
>
> There are a few notes here [1] including the pre-Apache release checklist.
> However, for the "pre-release" process, what has been done for earlier
> releases is the following:
> 1. Agree on a date to create the release branches. (I suggest ASAP for
> this one)
> 2. Keep accepting PRs on master and only backport bugfixes to the
> release branches. (this soak period is usually 1 week)
> 3. Start the release process.
>
> The release process includes creating the release notes, cutting the
> first RC0 and calling for a vote.
> We have [2] for instructions on validating a staged release.
>
> Creating the release notes is what takes most of our time.  For the
> past releases working with a Github Project helped a lot and allowed
> us to collaborate effectively.  However, Brennan has a tool that
> automates most of this.  He used it in the latest release.
> ,
>

1. https://cwiki.apache.org/confluence/display/NUTTX/Releases
> 2.
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
>
> On Thu, Apr 1, 2021 at 5:49 PM Alin Jerpelea  wrote:
> >
> > Hi Abdelaif,
> >
> > I think that we are in a better position now form a license perspective
> and
> > I can take the role as release manager for 10.1
> >
> >
> > Can you please point me to the checklist for the release
> >
> > Best regards
> > Alin
> >
> >
> > On Fri, Mar 19, 2021 at 8:46 PM Abdelatif Guettouche <
> > abdelatif.guettou...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Our latest release was on December 6th.  It's fair to say that we
> > > should start planning for NuttX-10.1.
> > >
> > > Last time Adam and Alin offered to be release managers, do you guys
> > > still want to do that?
> > >
> > > We can start by devising our plan and pick a date to create the
> branches.
> > >
>

Re: NuttX-10.1

[Alin Jerpelea]

I think that confluence is better for collaboration

Alin

On Mon, Apr 12, 2021, 06:29 Brennan Ashton 
wrote:

> On Sun, Apr 11, 2021 at 9:19 PM Nathan Hartman 
> wrote:
> >
> > On Mon, Apr 12, 2021 at 12:10 AM Brennan Ashton <
> bash...@brennanashton.com>
> > wrote:
> >
> > > I generated the project board for all the OS PRs in this release
> > > cycle.  I already sorted out a bunch of minor ones, but there are
> > > around 1000PRs that came in this cycle.
> > > https://github.com/apache/incubator-nuttx/projects/9
> > >
> > > Nathan in the past you have created the confluence page to add these
> > > to, do you want to do that again?  Might be easier if we tweaked it to
> > > be in markdown so there is less extra work converting it to markdown
> > > later?
> >
> >
> > Would it be better to write the release notes in the repo as markdown
> from
> > the start? I think in the past we discussed it, and it could save the
> extra
> > work of converting the format later. Thoughts?
>
> Confluence gives us the huge advantage of being able to collaborate on
> it in real time which we have really used in the previous cycles.  In
> confluence we can still have the markdown though, then it is just a
> simple copy at the end.
>
> --Brennan
>

Re: NuttX-10.1

[Alin Jerpelea]

The release notes are ready (just need alphabetical sorting) and we should
be ready to pack RC0.

Do we have a documented procedure how to create a release for NuttX and
upload it ?

Regards
Alin


On Wed, Apr 14, 2021, 10:46  wrote:

> Hi Nathan,
>
> Today I managed to log in to confluence without issues and work on some
> release notes
>
> Thanks
> Alin
>
>
> -Original Message-
> From: Nathan Hartman 
> Sent: den 13 april 2021 21:34
> To: dev@nuttx.apache.org
> Subject: Re: NuttX-10.1
>
> On Tue, Apr 13, 2021 at 1:43 PM Nathan Hartman 
> wrote:
> >
> > On Tue, Apr 13, 2021 at 11:12 AM  wrote:
> >>
> >> Hi Berenan,
> >>
> >> Since I did not manage to access confluence I finished sorting all
> >> PRs from the project board Please take a look and if possible
> >> transfer them to confluence
> >>
> >> Thanks
> >> Alin
> >
> >
> > Hi,
> >
> > I'm sorry to hear that. I don't know why the page won't load for you.
> Maybe the URL in the email got messed up somehow? Could you try to access
> the NuttX cwiki and navigate to the page using the navigation menu on the
> left? I think release notes (current and older) are under Project
> Administration or one of those subheadings toward the end.
> >
> > There shouldn't be any access restrictions on any of the cwiki pages.
> >
> > Unfortunately I am away from my machine today so I can't check what's
> going on with the page. If all else fails, feel free to create a new page
> and later I will manually merge the contents from the old one.
>
> I looked into it, and AFAICT you should be able to navigate to the cwiki
> page by going to the top page and using the navigation tree sidebar to go
> to:
>
> Project Administration -> Releases -> Release Notes -> NuttX 10.1
>
> or access the page at this link, (assuming it doesn't get messed up going
> through email):
>
>
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NUTTX/NuttX*10.1__;Kw!!JmoZiZGBv3RvKRSx!t1RTzXhLk5oX1B0dfJE2ChLvrVsVvsUCniHn8kGXYlkvHzvu8-xR3ruNq3-Eas0Mbw$
>
> I have just accessed this page without logging in, as an unauthenticated
> user, and from a different web browser than I normally use, to ensure there
> isn't some restriction on it.
>
> Please retry; if you have problems, check the URL (there is a '+'
> (plus) sign there and also a '.' (period); maybe that's causing
> problems?) and perhaps try clearing any stale browsing history... Let me
> know if the page is still inaccessible.
>
> Thanks,
> Nathan
>

[VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 10.1.0 RC0 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-RC0
  Hash for the release incubating-nuttx tag:
f380c919f04d5ee88e0a83f5632cc83af503664f
  Hash for the release incubating-nuttx-apps tag:
4348d91d1356335483089c3865282d80f13bedcd

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.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

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

[Alin Jerpelea]

Hi all,

The sum is reuploaded now seems to be ok
Thansk for reporing it

Regards
Alin


On Sun, Apr 18, 2021 at 7:25 PM Brennan Ashton 
wrote:

> On Sun, Apr 18, 2021 at 9:38 AM Abdelatif Guettouche
>  wrote:
> >
> > Is it just me or there is an issue with the checksum of the apps tar?
> >
>
> Alin,
> Can you check this an re-upload. You can verify locally as I showed here
>
> https://gist.github.com/btashton/ee474723013a7040186c91d41a4c7fad#check-the-release-artifacts
>
> After it is uploaded you can also run this script against the uploaded
> files, which is where we see the bad checksum.
>
> ❯ ./tools/checkrelease.sh --url
> https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0
> Downloading release files from
> https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/
> gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
> gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
> gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created
> gpg: key E1B6E30DB05D6280: public key "Brennan Ashton
> " imported
> gpg: key 9E711BAD3264C061: public key "Alin Jerpelea
> " imported
> gpg: Total number processed: 2
> gpg:   imported: 2
>  OK:
> https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/../KEYS
> is imported.
> Checking apache-nuttx-10.1.0-incubating.tar.gz sha512...
>  OK: apache-nuttx-10.1.0-incubating.tar.gz sha512 hash matches.
>
> Checking apache-nuttx-10.1.0-incubating.tar.gz GPG signature:
> gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT
> gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061
> gpg: Good signature from "Alin Jerpelea "
> [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D  E240 9E71 1BAD 3264 C061
>  OK: apache-nuttx-10.1.0-incubating.tar.gz gpg signature matches.
>
> Checking apache-nuttx-10.1.0-incubating.tar.gz for required files:
>  OK: all required files exist in nuttx.
>
> Checking apache-nuttx-apps-10.1.0-incubating.tar.gz sha512...
> sha512sum: WARNING: 1 computed checksum did NOT match
> apache-nuttx-apps-10.1.0-incubating.tar.gz: FAILED
>  - apache-nuttx-apps-10.1.0-incubating.tar.gz sha512 hash does not match.
>
> Checking apache-nuttx-apps-10.1.0-incubating.tar.gz GPG signature:
> gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT
> gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061
> gpg: Good signature from "Alin Jerpelea "
> [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D  E240 9E71 1BAD 3264 C061
>  OK: apache-nuttx-apps-10.1.0-incubating.tar.gz gpg signature matches.
>
> Checking apache-nuttx-apps-10.1.0-incubating.tar.gz for required files:
>  OK: all required files exist in apps.
>
> Trying to build nuttx sim:nsh...
>

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

[Alin Jerpelea]

Hi Brennan,
I think that we should backport them and I will cut RC1
Thanks
Alin


On Thu, Apr 22, 2021, 08:30 Brennan Ashton 
wrote:

> Alin,
> I think we should consider if we want to backport these into the
> 10.1.0 release.  I am still running more tests myself on all the
> hardware I have, but these seemed important to at least consider.
> https://github.com/apache/incubator-nuttx/pull/3586
> https://github.com/apache/incubator-nuttx/pull/3580
>
> --Brennan
>
> On Sun, Apr 18, 2021 at 7:06 AM Alin Jerpelea  wrote:
> >
> > Hello all,
> > Apache NuttX (Incubating) 10.1.0 RC0 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-RC0
> >   Hash for the release incubating-nuttx tag:
> > f380c919f04d5ee88e0a83f5632cc83af503664f
> >   Hash for the release incubating-nuttx-apps tag:
> > 4348d91d1356335483089c3865282d80f13bedcd
> >
> > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/
> > [2]
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.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
>

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

[Alin Jerpelea]

It is perfect timing!

I will cut RC1 with the fixes tonight

Thanks
Alin

On Thu, Apr 22, 2021, 16:12 Nathan Hartman  wrote:

> On Thu, Apr 22, 2021 at 2:54 AM Alin Jerpelea  wrote:
>
> > Hi Brennan,
> > I think that we should backport them and I will cut RC1
> > Thanks
> > Alin
>
>
>
> If I'm not too late, I fixed up the ReleaseNotes a little bit in PR-3570
>
>
>
>
> >
> >
> > On Thu, Apr 22, 2021, 08:30 Brennan Ashton 
> > wrote:
> >
> > > Alin,
> > > I think we should consider if we want to backport these into the
> > > 10.1.0 release.  I am still running more tests myself on all the
> > > hardware I have, but these seemed important to at least consider.
> > > https://github.com/apache/incubator-nuttx/pull/3586
> > > https://github.com/apache/incubator-nuttx/pull/3580
> > >
> > > --Brennan
> > >
> > > On Sun, Apr 18, 2021 at 7:06 AM Alin Jerpelea 
> > wrote:
> > > >
> > > > Hello all,
> > > > Apache NuttX (Incubating) 10.1.0 RC0 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-RC0
> > > >   Hash for the release incubating-nuttx tag:
> > > > f380c919f04d5ee88e0a83f5632cc83af503664f
> > > >   Hash for the release incubating-nuttx-apps tag:
> > > > 4348d91d1356335483089c3865282d80f13bedcd
> > > >
> > > > [1]
> https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/
> > > > [2]
> > >
> >
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.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
> > >
> >
>

Re: First time contributor PRs will need approval to run CI

[Alin Jerpelea]

Thanks for sharing

Regards
Alin

On Fri, Apr 23, 2021, 05:31 Nathan Hartman  wrote:

> On Thu, Apr 22, 2021 at 11:26 PM Brennan Ashton  >
> wrote:
>
> > Just as a heads up Github has implemented a change to help combat spam
> > accounts using our CI resources for crypto mining and the like.  I
> > don't know of any cases of this happening to this project, but many
> > other projects have been hit with this.
> >
> > Going forward the first time someone submits a PR a commiter will have
> > to manually approve the CI run.  Once they have a PR merged this
> > action will not be required again.
> >
> > You can read more about this here:
> >
> >
> https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks
> >
> > --Brennan
> >
>
> Thanks for the heads up!
>
> Nathan
>

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release

[Alin Jerpelea]

I will look into it ASAP
Regards
Alin

On Wed, Apr 28, 2021, 14:58 Gustavo Henrique Nihei 
wrote:

> Hi folks,
>
> I believe we should consider backporting the fix from this PR into the
> 10.1.0 release:
> https://github.com/apache/incubator-nuttx/pull/3614
>
> It fixes a side effect from the refactoring of the stack architecture
> due to a wrong stack alignment for RISC-V chips.
>
> Best regards,
> Gustavo.
>
> On Mon, Apr 26, 2021 at 5:58 AM  wrote:
> >
> > Hi Brenan,
> >
> > We still have the following commit that is not resolved and I think that
> it is better to hold the release until it is ready for emerge
> > https://github.com/apache/incubator-nuttx/pull/3601
> >
> > Regards
> > Alin
> >
> > -Original Message-
> > From: Alin Jerpelea 
> > Sent: den 22 april 2021 16:14
> > To: dev@nuttx.apache.org
> > Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
> >
> > It is perfect timing!
> >
> > I will cut RC1 with the fixes tonight
> >
> > Thanks
> > Alin
> >
> > On Thu, Apr 22, 2021, 16:12 Nathan Hartman 
> wrote:
> >
> > > On Thu, Apr 22, 2021 at 2:54 AM Alin Jerpelea 
> wrote:
> > >
> > > > Hi Brennan,
> > > > I think that we should backport them and I will cut RC1 Thanks Alin
> > >
> > >
> > >
> > > If I'm not too late, I fixed up the ReleaseNotes a little bit in
> > > PR-3570
> > >
> > >
> > >
> > >
> > > >
> > > >
> > > > On Thu, Apr 22, 2021, 08:30 Brennan Ashton
> > > > 
> > > > wrote:
> > > >
> > > > > Alin,
> > > > > I think we should consider if we want to backport these into the
> > > > > 10.1.0 release.  I am still running more tests myself on all the
> > > > > hardware I have, but these seemed important to at least consider.
> > > > > https://urldefense.com/v3/__https://github.com/apache/incubator-nu
> > > > > ttx/pull/3586__;!!JmoZiZGBv3RvKRSx!rb2nGxDcx1NeBVx6ZgXhc6ZY2nV6G_l
> > > > > kT8Y8QJWo9Nv_bGYGjtgmeOc3mRLLOLl7Nw$
> > > > > https://urldefense.com/v3/__https://github.com/apache/incubator-nu
> > > > > ttx/pull/3580__;!!JmoZiZGBv3RvKRSx!rb2nGxDcx1NeBVx6ZgXhc6ZY2nV6G_l
> > > > > kT8Y8QJWo9Nv_bGYGjtgmeOc3mRKshpGeRw$
> > > > >
> > > > > --Brennan
> > > > >
> > > > > On Sun, Apr 18, 2021 at 7:06 AM Alin Jerpelea 
> > > > wrote:
> > > > > >
> > > > > > Hello all,
> > > > > > Apache NuttX (Incubating) 10.1.0 RC0 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-RC0
> > > > > >   Hash for the release incubating-nuttx tag:
> > > > > > f380c919f04d5ee88e0a83f5632cc83af503664f
> > > > > >   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-RC0/__;!!JmoZiZGBv3RvKRSx!rb2nGxDcx1NeBVx6ZgXhc6ZY
> > > 2nV6G_lkT8Y8QJWo9Nv_bGYGjtgmeOc3mRIUEGmDag$
> > > > > > [2]
> > > > >
> > > >
> > > https://urldefense.com/v3/__https://raw.githubusercontent.com/apache/i
> > > ncubator-nuttx/nuttx-10.1.0-RC0/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!rb2n
> > > GxDcx1NeBVx6ZgXhc6ZY2nV6G_lkT8Y8QJWo9Nv_bGYGjtgmeOc3mRJlgBtnkg$
> > > > > > [3]
> > > > > > https://urldefense.com/v3/__https://www.apache.org/dev/release.h
> > > > > > tml*approving-a-release__;Iw!!JmoZiZGBv3RvKRSx!rb2nGxDcx1NeBVx6Z
> > > > > > gXhc6ZY2nV6G_lkT8Y8QJWo9Nv_bGYGjtgmeOc3mRJEiqu7OA$
> > > > > > [4]
> > > > >
> > > >
> > > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/displa
> > > y/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!rb2nGxDcx
> > > 1NeBVx6ZgXhc6ZY2nV6G_lkT8Y8QJWo9Nv_bGYGjtgmeOc3mRJsl8kw8w$
> > > > >
> > > >
> > >
>
>
>
> --
> Gustavo Henrique Nihei
>

[VOTE] Apache NuttX 10.1.0 (incubating) RC1 release

[Alin Jerpelea]

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:
4348d91d1356335483089c3865282d80f13bedcd
  Hash for the release incubating-nuttx-apps tag:
112d709609e4916b21e435152679cd0b5f3177fb

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release

[Alin Jerpelea]

I created the PR for this fix and I will create RC again if there are no
other concerns

Thanks
Alin

On Sat, May 1, 2021, 14:13 Alan Carvalho de Assis  wrote:

> Yes, this fix is important for all RISC-V MCUs
>
> BR,
>
> Alan
>
> On Saturday, May 1, 2021, Gustavo Henrique Nihei 
> wrote:
>
> > Hi folks,
> >
> > I believe we still need to backport this PR
> > https://github.com/apache/incubator-nuttx/pull/3636 (already labelled)
> > It is a complement to
> > https://github.com/apache/incubator-nuttx/pull/3614, which has been
> > recently backported.
> > Both address the issue of stack alignment for RISC-V chips.
> >
> > Best regards,
> > Gustavo.
> >
> > On Sat, May 1, 2021 at 3:50 AM Alin Jerpelea  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:
> > > 4348d91d1356335483089c3865282d80f13bedcd
> > >   Hash for the release incubating-nuttx-apps tag:
> > > 112d709609e4916b21e435152679cd0b5f3177fb
> > >
> > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/
> > > [2]https://raw.githubusercontent.com/apache/
> > incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes
> > > [3] https://www.apache.org/dev/release.html#approving-a-release
> > > [4]https://cwiki.apache.org/confluence/display/NUTTX/
> > Validating+a+staged+Release
> >
> >
> >
> > --
> > Gustavo Henrique Nihei
> >
>

Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release

[Alin Jerpelea]

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://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release


On Sat, May 1, 2021 at 2:54 PM Alin Jerpelea  wrote:

> I created the PR for this fix and I will create RC again if there are no
> other concerns
>
> Thanks
> Alin
>
> On Sat, May 1, 2021, 14:13 Alan Carvalho de Assis 
> wrote:
>
>> Yes, this fix is important for all RISC-V MCUs
>>
>> BR,
>>
>> Alan
>>
>> On Saturday, May 1, 2021, Gustavo Henrique Nihei 
>> wrote:
>>
>> > Hi folks,
>> >
>> > I believe we still need to backport this PR
>> > https://github.com/apache/incubator-nuttx/pull/3636 (already labelled)
>> > It is a complement to
>> > https://github.com/apache/incubator-nuttx/pull/3614, which has been
>> > recently backported.
>> > Both address the issue of stack alignment for RISC-V chips.
>> >
>> > Best regards,
>> > Gustavo.
>> >
>> > On Sat, May 1, 2021 at 3:50 AM Alin Jerpelea 
>> 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:
>> > > 4348d91d1356335483089c3865282d80f13bedcd
>> > >   Hash for the release incubating-nuttx-apps tag:
>> > > 112d709609e4916b21e435152679cd0b5f3177fb
>> > >
>> > > [1]
>> https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/
>> > > [2]https://raw.githubusercontent.com/apache/
>> > incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes
>> > > [3] https://www.apache.org/dev/release.html#approving-a-release
>> > > [4]https://cwiki.apache.org/confluence/display/NUTTX/
>> > Validating+a+staged+Release
>> >
>> >
>> >
>> > --
>> > Gustavo Henrique Nihei
>> >
>>
>

[RESULT] [VOTE] Release Apache NuttX (Incubating) 10.1.0 [RC1]

[Alin Jerpelea]

Hi,



The vote closes now as over 72hr have passed. The vote PASSES with 6

(+4 non-binding) votes from the PPMC,

0 (+1 binding) vote from the IPMC,

2 (+0 non-binding) votes from the developer community,

No further +1, 0 or -1 votes.



The vote thread:

[1]

https://lists.apache.org/thread.html/ra60b4173945cfd2a33924cc8d707863039c1764a7ea8e47a1d8502a0%40%3Cdev.nuttx.apache.org%3E



I will now bring the vote to gene...@incubator.apache.org to get

approval by the IPMC.

If this vote passes also, the release is accepted and will be

published.



Thanks,

Alin Jerpelea

[ANNOUNCE] Apache NuttX 10.1.0-incubating released

[Alin Jerpelea]

The Apache NuttX (incubating) project team is proud to announce that
Apache NuttX 10.1.0-incubating has been released.

The release artifacts and Release Notes can be found at:
https://nuttx.apache.org/download/
https://nuttx.apache.org/releases/10.1.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: Workshop: Put on nuttx.apache.org?

[Alin Jerpelea]

Hi,
I agree with Alan, I think that "events.nuttx" is a dynamic page that will
help us keep the community updated and propagate the changes with a fast
pase
In my opinion this page should be linked from the main Apache on

Thanks
Alin


On Thu, Aug 26, 2021 at 12:49 PM Alan Carvalho de Assis 
wrote:

> Sorry the typo, should be: I'm not against neither very excited about it.
>
> On 8/26/21, Alan Carvalho de Assis  wrote:
> > Hi Nathan,
> >
> > I'm against it or very excited about it. I think we decided to created
> > the https://nuttx.events some years ago to have something more dynamic
> > that we could access easily. Also you know: never put all your eggs in
> > the same basket.
> >
> > If you decide to do it I can send you the files and links.
> >
> > BR,
> >
> > Alan
> >
> > On 8/25/21, Nathan Hartman  wrote:
> >> Is anyone opposed to linking the workshop videos from the NuttX website?
> >>
> >> I think it might be a good thing to have a page per workshop (this
> >> year's, last year's, etc) with the links to the videos, and to have
> >> the latest one mentioned on the front page.
> >>
> >> Cheers,
> >> Nathan
> >>
> >
>

Re: NuttX Monthly Meetup

[Alin Jerpelea]

It is a an open meet and the plan is to discuss any topics (open issues,
plans, wishes)

I will talk about license issues and next NuttX release





On Wed, Sep 22, 2021, 21:41 Tim Hardisty  wrote:

> What sort of agenda, or purpose, Alan?
>
> Sounds like a good idea but some suggestion of what to expect would be
> good :)
>
>
>
> On 22/09/2021, 18:20, "Alan Carvalho de Assis"  wrote:
>
> Dear NuttXers,
>
> We want to do monthly meets with our developers and users.
>
> The first online meet will be this Friday (2021/09/24) at 18:00 GMT.
>
> Everybody can join using this link:
>
> https://meet.jit.si/NuttXMeetup
>
> BR,
>
> Alan
>
>
>

Re: NuttX Monthly Meetup

[Alin Jerpelea]

MOM jitsi meet 24.09.2021

License updates
Alin asked for contact ideas for
Haltian and Omni Hooverboards
waiting for Adam Dunkels to answer
have an progress update regarding the license status

Alin is planing to create the next release
we will start the release process for NuttX 10.2 with mixed licenses
Aim to release NuttX 11.0 with Apache licenses

Todo:
ping Bernan to create the release notes for NuttX 10.2

New features/suggestions
toochain base on Clang. we should try to suport it
improve build time on non linux systems
explore AI - tensorflow, NNabla interation
explore MicroROS integration

questionaire to understand what OS are people using
windows native / windows cygwin / linux / Mac

Topic for the next meeting
Cmake - should we switch or not?

October 22 next online Meeting

On Thu, Sep 23, 2021 at 5:35 AM Alin Jerpelea  wrote:

> It is a an open meet and the plan is to discuss any topics (open issues,
> plans, wishes)
>
> I will talk about license issues and next NuttX release
>
>
>
>
>
> On Wed, Sep 22, 2021, 21:41 Tim Hardisty  wrote:
>
>> What sort of agenda, or purpose, Alan?
>>
>> Sounds like a good idea but some suggestion of what to expect would be
>> good :)
>>
>>
>>
>> On 22/09/2021, 18:20, "Alan Carvalho de Assis" 
>> wrote:
>>
>> Dear NuttXers,
>>
>> We want to do monthly meets with our developers and users.
>>
>> The first online meet will be this Friday (2021/09/24) at 18:00 GMT.
>>
>> Everybody can join using this link:
>>
>> https://meet.jit.si/NuttXMeetup
>>
>> BR,
>>
>> Alan
>>
>>
>>

Re: Which control version software are you using? //was Re: Poll: Which OS are you using to compile NuttX?

[Alin Jerpelea]

git and linux

On Sat, Sep 25, 2021 at 9:02 AM Simon Filgis 
wrote:

> What does your script do?
>
> David S. Alessio  schrieb am Sa., 25. Sept.
> 2021, 01:02:
>
> > I’d like to see my git version script be brought back into mainstream.
> >
> > > On Sep 24, 2021, at 3:58 PM, Alan Carvalho de Assis  >
> > wrote:
> > >
> > > Hi David,
> > >
> > > Nice you hear from you.
> > >
> > > I'm also using git: #1
> > >
> > > BR,
> > >
> > > Alan
> > >
> > > On 9/24/21, David S. Alessio  wrote:
> > >> Hi, Alan,
> > >>
> > >> It’d be good to know how developers are managing their code:
> > >> 1) git
> > >> 2) mercurial
> > >> 3) SVN
> > >> 4) zip files on floppies
> > >> 5) none
> > >>
> > >> My money is on #1 ;)
> > >>
> > >> Cheers,
> > >> -david
> > >>
> > >>> On Sep 24, 2021, at 2:07 PM, Alan Carvalho de Assis <
> acas...@gmail.com
> > >
> > >>> wrote:
> > >>>
> > >>> Hi Flávio,
> > >>>
> > >>> That is good idea, but I think we need to have some kind of
> > maintainers.
> > >>>
> > >>> It is hard when someone adds some strange OS and the go out and leave
> > >>> it to other developers to maintain it.
> > >>>
> > >>> Do you want to mainline some host OS? :-P
> > >>>
> > >>> BR,
> > >>>
> > >>> Alan
> > >>>
> > >>> On 9/24/21, Flavio Castro Alves Filho 
> wrote:
> >  Alan,
> > 
> >  How about a poll asking "which other OS would you like to build
> > NuttX?"
> >  :-P
> > 
> >  Best regards,
> > 
> >  Flavio
> > 
> >  Em sex., 24 de set. de 2021 às 17:45, Tim Hardisty
> >   escreveu:
> > >
> > > Linux
> > >
> > >
> > >
> > > On 24/09/2021, 21:07, "Alan Carvalho de Assis"  >
> > > wrote:
> > >
> > >   Sorry guys, I suppose you are using LinkedIn too.
> > >
> > >   Yes, probably it will collect some data from you, but you are
> using
> > > a
> > >   better MS gather:
> > >
> > >   "Sent from Mail for Windows"
> > >
> > >   So, if you are already in the hell, please give a warm hug in the
> > > Lucifer :-D
> > >
> > >   Now, let be serious here: for those who don't have LinkedIn
> access,
> > >   please reply this email with one of these options:
> > >
> > >   1) Linux
> > >   2) MacOS
> > >   3) Windows using Cygwin
> > >   4) Windows Native
> > >
> > >   Thank you for the understanding.
> > >
> > >   BR,
> > >
> > >   Alan
> > >
> > >   On 9/24/21, Russell Haley  wrote:
> > >> The link gives me “This post cannot be displayed”. I am logged
> into
> > > the
> > >> Microsoft data collection site known as LinkedIn.
> > >>
> > >> Sent from Mail for Windows
> > >>
> > >> From: Tim Hardisty
> > >> Sent: Friday, September 24, 2021 12:54 PM
> > >> To: dev@nuttx.apache.org
> > >> Subject: Re: Poll: Which OS are you using to compile NuttX?
> > >>
> > >> Needs a LinkedIn login?
> > >>
> > >>
> > >>
> > >> From: Alan Carvalho de Assis 
> > >> Reply to: "dev@nuttx.apache.org" 
> > >> Date: Friday, 24 September 2021 at 20:20
> > >> To: dev 
> > >> Subject: Poll: Which OS are you using to compile NuttX?
> > >>
> > >> Hi Everyone, Please help us to discover which OS people are using
> > > most to
> > >> compile NuttX:
> > >>
> > >
> >
> https://www.linkedin.com/feed/update/urn:li:activity:6847246067046596609/
> > > It
> > >> will help us to decide how better support your host OS. BR, Alan
> > >>
> > >>
> > >
> > >
> > 
> > 
> >  --
> >  Flavio de Castro Alves Filho
> > 
> >  flavio.al...@gmail.com
> >  Twitter: http://twitter.com/#!/fraviofii
> >  LinkedIn profile: www.linkedin.com/in/flaviocastroalves
> > 
> > >>
> > >>
> >
> >
>

Re: NuttX Monthly Meetup

[Alin Jerpelea]

I am sorry if you feel like this. The meeting was open for anyone willing
to participate but we  will stop the meetings if this is against the rules.

Best Regards
Alin

On Sat, Sep 25, 2021, 13:47 spudaneco  wrote:

> This is not "helping users",  These are all project management topics.
> These kinds of discussions are not appropriate outside of ASF provided
> communication mechanism.  You cannot create your own private project
> management team that excludes everyone else.Sent from my Galaxy
>  Original message ----From: Alin Jerpelea 
> Date: 9/25/21  1:11 AM  (GMT-06:00) To: dev@nuttx.apache.org Subject: Re:
> NuttX Monthly Meetup MOM jitsi meet 24.09.2021License updatesAlin asked for
> contact ideas forHaltian and Omni Hooverboardswaiting for Adam Dunkels to
> answerhave an progress update regarding the license statusAlin is planing
> to create the next releasewe will start the release process for NuttX 10.2
> with mixed licensesAim to release NuttX 11.0 with Apache licensesTodo:ping
> Bernan to create the release notes for NuttX 10.2New
> features/suggestionstoochain base on Clang. we should try to suport
> itimprove build time on non linux systemsexplore AI - tensorflow, NNabla
> interationexplore MicroROS integrationquestionaire to understand what OS
> are people usingwindows native / windows cygwin / linux / MacTopic for the
> next meetingCmake - should we switch or not?October 22 next online
> MeetingOn Thu, Sep 23, 2021 at 5:35 AM Alin Jerpelea 
> wrote:> It is a an open meet and the plan is to discuss any topics (open
> issues,> plans, wishes)>> I will talk about license issues and next NuttX
> release>>>>>> On Wed, Sep 22, 2021, 21:41 Tim Hardisty
>  wrote:>>> What sort of agenda, or purpose,
> Alan?>>>> Sounds like a good idea but some suggestion of what to expect
> would be>> good :)>>>>>>>> On 22/09/2021, 18:20, "Alan Carvalho de Assis" <
> acas...@gmail.com>>> wrote:>>>> Dear NuttXers,>>>> We want to do
> monthly meets with our developers and users.>>>> The first online meet
> will be this Friday (2021/09/24) at 18:00 GMT.>>>> Everybody can join
> using this link:>>>> https://meet.jit.si/NuttXMeetup>>>>
> BR,>>>> Alan>>>>>>

Re: NuttX-10.2 release

[Alin Jerpelea]

since none opposed to the release here my proposal for the release schedule:

  w40 -- Master Stability Window (keep the merging of risky PRs to a
minimum this week)
  W41.1 -- Create the 10.2 release branch
  w41-42 -- Stabilize / test / release notes
  w43.1 -- Tag RC0 and call for PPMC / Community Vote
  w44(or when we have the votes) Call for IPMC Vote
  w45 -- Update site and announce (we have to wait for download
mirrors to sync).


On Thu, Sep 30, 2021 at 9:57 AM  wrote:

> Hi,
>
> Our latest release 10.1 was on 2021-05-26.
>
> I think that is time to create the branches and the release notes.
>
> @Brennan Ashton can you please create
> the draft release notes
>
> I offer to be the release manager for this release
>
> Best regards
> Alin
>
>

Re: NuttX-10.2 release

[Alin Jerpelea]

releases/10.2 branch has been created. Please start testing the branch on
various HW.

Best regards
Alin


On Tue, Oct 12, 2021 at 11:57 AM  wrote:

> In my opinion is better to work on release notes with wiki then copy paste
> them to a file in each release
> I think that is also beneficial for people that download the zip and will
> use it without internet access
>
> //Alin
>
> -Original Message-
> From: Abdelatif Guettouche 
> Sent: den 12 oktober 2021 11:45
> To: Jerpelea, Alin 
> Cc: Nathan Hartman ; Brennan Ashton <
> bash...@brennanashton.com>; dev@nuttx.apache.org
> Subject: Re: NuttX-10.2 release
>
> You mean we drop the ReleaseNote file?
>
> We do need to have the notes versioned with the rest of the code.
> What was suggested before is to use Markdown for both Confluence and
> ReleaseNote and then it's just a matter of copy/paste.
> What also can be done to make it easy, is to only keep the latest release
> notes on the top level file.  One could checkout to a specific release
> branch to inspect the release notes.
> I think a few didn't agree with this and argued that we need all the
> release notes, I guess in this case we can move the old release notes to a
> releasenotes.d folder of some sort.  For me keeping all the release notes
> in one file is getting hard to maintain, and we need to do something about
> it.
>
> On Tue, Oct 12, 2021 at 10:37 AM  wrote:
> >
> > I propose that we work on wiki to create the release notes What do you
> > say?
> >
> > Thanks
> > Alin
> >
> >
> > -Original Message-
> > From: Abdelatif Guettouche 
> > Sent: den 12 oktober 2021 09:22
> > To: Jerpelea, Alin 
> > Cc: Nathan Hartman ; Brennan Ashton
> > ; dev@nuttx.apache.org
> > Subject: Re: NuttX-10.2 release
> >
> > > Is there a tool to migrate the notes from github to cwiki?
> >
> > Do you mean from Confluence to Github (i.e. ReleaseNotes file)?  If so,
> no there isn't.  One thing we can do is to change the syntax to Markdown so
> we can just copy/paste.
> >
> > BTW, regarding the changes documented in  Confluence, this:
> > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/displa
> > y/NUTTX/NuttX*10.2*changes-to-build-system__;KyM!!JmoZiZGBv3RvKRSx!tJy
> > 3l96vFgH7-sGLU_8t8T8fRPm4IUGy5hIS8KhNRfjNiIE9NJoapeDV14m-LWStzw$
> > has been reverted.  Or at least part of it if I recall correctly.
> >
> > On Tue, Oct 12, 2021 at 9:16 AM  wrote:
> > >
> > > Hi Nathan
> > >
> > >
> > >
> > > Is there a tool to migrate the notes from github to cwiki?
> > >
> > >
> > >
> > > Thanks
> > >
> > > Alin
> > >
> > >
> > >
> > >
> > >
> > > From: Nathan Hartman 
> > > Sent: den 12 oktober 2021 06:14
> > > To: Jerpelea, Alin 
> > > Cc: abdelatif.guettou...@gmail.com; bash...@brennanashton.com;
> > > dev@nuttx.apache.org
> > > Subject: Re: NuttX-10.2 release
> > >
> > >
> > >
> > > Please note, there is already a draft Release Notes page at the
> following link. Commits that required compatibility changes are already
> documented there:
> > >
> > >
> > >
> > > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/disp
> > > la
> > > y/NUTTX/NuttX*10.2__;Kw!!JmoZiZGBv3RvKRSx!tJy3l96vFgH7-sGLU_8t8T8fRP
> > > m4 IUGy5hIS8KhNRfjNiIE9NJoapeDV14nZ0Kzw0w$
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Oct 11, 2021 at 2:59 AM  wrote:
> > >
> > > Hello all
> > > According to the proposed plan I will create the 10.2 branches today
> > >
> > > @Brennan Ashton @Nathan Hartman @Abdelatif Guettouche Can you please
> > > generate the RAW release notes so that I can continue
> > >
> > > Thanks
> > > Alin
> > >
> > > -Original Message-
> > > From: Alin Jerpelea 
> > > Sent: den 4 oktober 2021 08:37
> > > To: dev@nuttx.apache.org
> > > Subject: Re: NuttX-10.2 release
> > >
> > > since none opposed to the release here my proposal for the release
> schedule:
> > >
> > >   w40 -- Master Stability Window (keep the merging of risky PRs to a
> minimum this week)
> > >   W41.1 -- Create the 10.2 release branch
> > >   w41-42 -- Stabilize / test / release notes
> > >   w43.1 -- Tag RC0 and call for PPMC / Community Vote
> > >   w44(or when we have the votes) Call for IPMC Vote
> > >   w45 -- Update site and announce (we have to wait for download
> mirrors to sync).
> > >
> > >
> > > On Thu, Sep 30, 2021 at 9:57 AM  wrote:
> > >
> > > > Hi,
> > > >
> > > > Our latest release 10.1 was on 2021-05-26.
> > > >
> > > > I think that is time to create the branches and the release notes.
> > > >
> > > > @Brennan Ashton<mailto:bash...@brennanashton.com> can you please
> > > > create the draft release notes
> > > >
> > > > I offer to be the release manager for this release
> > > >
> > > > Best regards
> > > > Alin
> > > >
> > > >
>

Re: github nuttx/nuttx vs apache/incubator-nuttx

[Alin Jerpelea]

I propose that we delete the contents of https://github.com/NuttX/ and we
host there only the components that have conflicting licenses under
https://github.com/NuttX/nuttx-extras



On Sun, Oct 17, 2021, 06:45 Xiang Xiao  wrote:

> Some tools(e.g. kconfig-frontend) are critical for NuttX, but in an
> unmaintained state, so we have to maintain our own version.
> Two options here:
>
>1. Host on https://bitbucket.org/nuttx/, Greg needs to share the admin
>right to all PPMC/Commmiter member.
>2. Host on  https://github.com/NuttX/ ,
>Remove no PPMC/Commiter from admin group
>
> Either way is fine, but we need action now. I have seen the same topic
> happen on the email list many times, but nothing happens after that
> discussion.
>
> On Sun, Oct 17, 2021 at 1:26 AM Brennan Ashton 
> wrote:
>
> > Agreed it will just complicate things moving towards graduation. I had
> > asked for it to be taken down a long time ago.
> >
> > --Brennan
> >
> > On Sat, Oct 16, 2021, 7:10 AM Gregory Nutt  wrote:
> >
> > > No, https://github.com/NuttX/nuttx is just garbage and should be
> > deleted.
> > > It has nothing to do with Apache NuttX and I don't think anything has
> > been
> > > touched there in months.
> > >
> > > A thought was that this could be a place to keep GPL tools and
> > applications
> > > that are needed with NuttX but that are incompatible with the ASF
> > project.
> > > This is where a tool like kconfig-frontends could be supported,
> > >
> > > A problem now is that many people have access to the repository and it
> is
> > > not under the control of any project.
> > >
> > >
> > > On Sat, Oct 16, 2021 at 7:53 AM Tomasz CEDRO  wrote:
> > >
> > > > Hello world :-)
> > > >
> > > > Another thing I found confusing a bit for a newcomer is the dual
> > > > repository model:
> > > > 1. https://github.com/NuttX/nuttx
> > > > 2. https://github.com/apache/incubator-nuttx
> > > >
> > > > There is not information or redirect on 1 that development takes
> place
> > on
> > > > 2.
> > > >
> > > > Is 2 going to become 1 back again when incubation is complete? :-)
> > > >
> > > > --
> > > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> > > >
> > >
> >
>

Re: github nuttx/nuttx vs apache/incubator-nuttx

[Alin Jerpelea]

Thanks for cleaning it out


On Sun, Oct 17, 2021, 20:17 Gregory Nutt  wrote:

> All of the junk repositories are gone (that is a good thing to do
> regardless of what we decide to do with the directory).  The
> github.com/nuttx directory still exists.  The following people have write
> access:
>
>- Alan Carvalho de Assis, acassis
>- Anthony Merlino,antmerlino
>- David Sidrane, davids5
>- hartmannathan
>- liuguo09
>- lAbdelatif Guettouche, Ouss4
>- patacongo
>- Xiang Xiao, xiaoxiang781216
>
> We can add more if we decide to use the directory.  Or we can remove the
> directory if we decide we don't need it.
>
> While this does not resolve the important issue at hand, it does at least
> resolve newbies being confused as Tomasz was.
>
> On Sun, Oct 17, 2021 at 12:02 PM Gregory Nutt  wrote:
>
> > I will go ahead and remove github.com/nuttx content.  There is nother
> > there of value now and everything is available elsewhere.  So that is
> safe
> > to do in any case.
> >
>

[VOTE] Apache NuttX 10.2.0 (incubating) RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 10.2.0 RC0 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.2.0-RC0
  Hash for the release incubating-nuttx tag:
  3fede42098e5883f336d846ac30edfe749899494
  Hash for the release incubating-nuttx-apps tag:
  562239ecb2d84dd9de2dd206da41df19602e20cb

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.2.0-RC0/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.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

Re: NuttX Logo

[Alin Jerpelea]

Thanks for sharing it

On Sun, Nov 7, 2021, 13:52 Alan Carvalho de Assis  wrote:

> Hi Everyone,
>
> Case someone needs the NuttX Logo, I created a vector image and Greg
> asked to put it as Apache Logos site:
>
> https://apache.org/logos/#nuttx
>
> Direct link:
> https://svn.apache.org/repos/asf/comdev/project-logos/originals/nuttx.svg
>
> It is basically the same logo, just a little bit cleaner ("Firefoxation").
>
> BR,
>
> Alan
>

[ANNOUNCE] Apache NuttX 10.2.0-incubating released

[Alin Jerpelea]

The Apache NuttX (incubating) project team is proud to announce
Apache NuttX 10.2.0-incubating has been released.

The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/10.2.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: Move to C99 for common code

[Alin Jerpelea]

In my opinion we should try to keep all platforms and avoid breaking them
by adopting new standards

An option would be to add the C99 as a menu option while keeping the
current compilers compatibility

Best Regards
Alin


On Sat, 8 Jan 2022, 13:53 Gregory Nutt,  wrote:

> z80 holds all 8-bit ZiLOG architectures.  That means
>
> z80 using the SDCC compiler
> z180 using the SDCC compiler
> ez80 which normally uses the ZiLOG compiler, but there is an experimental
> version of GCC for the ez80
>
> z16 uses only ZiLOG compiler
>
> Also consider SH1
>
> This will also require changes to INVIOLABLES.md and the coding standard.
> I would also recommend a formal vote to assure that you are following the
> will of the user base and not a personal agenda.  There used to be a small
> but important group of retro computer folk using NuttX; this eliminates
> support for them. There is language in the INVIOLABLES that is there
> specifically to protect them from actions like this.
>
> I have not heard of anyone using these architectures recently.  I would say
> that only ez80 is active with active development boards.  There are
> occasional developments with z180-like hardware.
>
> On Fri, Jan 7, 2022 at 11:40 PM Xiang Xiao 
> wrote:
>
> > Ceva we just added this week also supports C99, so we just need to check
> > avr, misoc, or1k, z16 and z80.
> >
> > On Sat, Jan 8, 2022 at 1:35 PM Petro Karashchenko <
> > petro.karashche...@gmail.com> wrote:
> >
> > > In addition I just checked latest GCC with HC12 support is 3.0.4
> version.
> > > It have C99 integrated. Will check with AVR32, but will probably need
> > some
> > > help with others.
> > >
> > > Best regards,
> > > Petro
> > >
> > > On Sat, Jan 8, 2022, 7:15 AM Petro Karashchenko <
> > > petro.karashche...@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > What about inline functions? Those are also a part on C99.
> > > >
> > > > Are those old architectures checked by the CI? I mean do we have a
> > proof
> > > > that those are still compilable with the latest release?
> > > >
> > > > Best regards,
> > > > Petro
> > > >
> > > > On Sat, Jan 8, 2022, 6:37 AM Xiang Xiao 
> > > wrote:
> > > >
> > > >>
> > > >>
> > > >> On Sat, Jan 8, 2022 at 6:29 AM Petro Karashchenko <
> > > >> petro.karashche...@gmail.com> wrote:
> > > >>
> > > >>> Hello team,
> > > >>>
> > > >>> Recently I mr. @Xiang Xiao  had a
> > > discussion
> > > >>> in one of the PR's related to C89 code compliance. Particularly
> > > related to
> > > >>> initializing a structure by field names (designated initializers).
> > Mr.
> > > @Xiang
> > > >>> Xiao  pointed out that "for the common
> > code
> > > >>> it is better to avoid C99 only features".
> > > >>> I examined the current NuttX code and see that currently common
> code
> > is
> > > >>> far away from C89 already and things like "",
> > > "",
> > > >>> "snprintf", "designated initializers", "__VA_ARGS__" (variadic
> macro)
> > > are
> > > >>> deeply embedded into the code.
> > > >>>
> > > >>>
> > > >> We need separate the features that come from the compiler and the
> > > >> standard library. Since the libc is provided by NuttX self:
> > > >>
> > > >>1. The header files(e.g.stdbool.h, intttyes.h) and function(e.g.
> > > >>snprintf) can be used in common code since NuttX can provide the
> > > >>implementation for all arch even the arch use a very old compiler
> > > >>2. The preprocessor (e.g.  __VA_ARGS__) or language( designated
> > > >>initializers) feature need to avoid or incorporate into the
> > > conditional
> > > >>macro
> > > >>
> > > >> .
> > > >>
> > > >>> I would like to come up with the suggestion to make C99 as a
> > > >>> prerequisite for the compiler that is used to build NuttX code.
> > > >>>
> > > >>
> > > >> As Greg said, if compilers used on all arch supported by NuttX
> support
> > > >> C99, there is no reason to limit us to C89. The compiler status is a
> > > >> keypoint.
> > > >>
> > > >>
> > > >>>
> > > >>> Best regards,
> > > >>> Petro
> > > >>>
> > > >>>
> > >
> >
>

Re: Move to C99 for common code

[Alin Jerpelea]

that code duplication is the way I was thinking if we want to be able to
use both compilers and keep all platforms
Best Regards
Alin

On Sat, 8 Jan 2022, 14:42 Alan Carvalho de Assis,  wrote:

> Hi Alin,
>
> using a menu option in this case will not work because the point is
> not passing a std c99 flag to the compiler, but using some C99
> features in the source code to simplify it.
>
> For example: the designated initializer list:
>
> struct test_s test =
>   {
> .second = 2,
> .first =  1
>   };
>
> It is not supported by C89 and adding an entry in the menuconfig will
> require duplication in the source code to support both standards (C89
> and C99).
>
> BR,
>
> Alan
>
> On 1/8/22, Alin Jerpelea  wrote:
> > In my opinion we should try to keep all platforms and avoid breaking them
> > by adopting new standards
> >
> > An option would be to add the C99 as a menu option while keeping the
> > current compilers compatibility
> >
> > Best Regards
> > Alin
> >
> >
> > On Sat, 8 Jan 2022, 13:53 Gregory Nutt,  wrote:
> >
> >> z80 holds all 8-bit ZiLOG architectures.  That means
> >>
> >> z80 using the SDCC compiler
> >> z180 using the SDCC compiler
> >> ez80 which normally uses the ZiLOG compiler, but there is an
> experimental
> >> version of GCC for the ez80
> >>
> >> z16 uses only ZiLOG compiler
> >>
> >> Also consider SH1
> >>
> >> This will also require changes to INVIOLABLES.md and the coding
> standard.
> >> I would also recommend a formal vote to assure that you are following
> the
> >> will of the user base and not a personal agenda.  There used to be a
> >> small
> >> but important group of retro computer folk using NuttX; this eliminates
> >> support for them. There is language in the INVIOLABLES that is there
> >> specifically to protect them from actions like this.
> >>
> >> I have not heard of anyone using these architectures recently.  I would
> >> say
> >> that only ez80 is active with active development boards.  There are
> >> occasional developments with z180-like hardware.
> >>
> >> On Fri, Jan 7, 2022 at 11:40 PM Xiang Xiao 
> >> wrote:
> >>
> >> > Ceva we just added this week also supports C99, so we just need to
> >> > check
> >> > avr, misoc, or1k, z16 and z80.
> >> >
> >> > On Sat, Jan 8, 2022 at 1:35 PM Petro Karashchenko <
> >> > petro.karashche...@gmail.com> wrote:
> >> >
> >> > > In addition I just checked latest GCC with HC12 support is 3.0.4
> >> version.
> >> > > It have C99 integrated. Will check with AVR32, but will probably
> need
> >> > some
> >> > > help with others.
> >> > >
> >> > > Best regards,
> >> > > Petro
> >> > >
> >> > > On Sat, Jan 8, 2022, 7:15 AM Petro Karashchenko <
> >> > > petro.karashche...@gmail.com> wrote:
> >> > >
> >> > > > Hi,
> >> > > >
> >> > > > What about inline functions? Those are also a part on C99.
> >> > > >
> >> > > > Are those old architectures checked by the CI? I mean do we have a
> >> > proof
> >> > > > that those are still compilable with the latest release?
> >> > > >
> >> > > > Best regards,
> >> > > > Petro
> >> > > >
> >> > > > On Sat, Jan 8, 2022, 6:37 AM Xiang Xiao <
> xiaoxiang781...@gmail.com>
> >> > > wrote:
> >> > > >
> >> > > >>
> >> > > >>
> >> > > >> On Sat, Jan 8, 2022 at 6:29 AM Petro Karashchenko <
> >> > > >> petro.karashche...@gmail.com> wrote:
> >> > > >>
> >> > > >>> Hello team,
> >> > > >>>
> >> > > >>> Recently I mr. @Xiang Xiao  had a
> >> > > discussion
> >> > > >>> in one of the PR's related to C89 code compliance. Particularly
> >> > > related to
> >> > > >>> initializing a structure by field names (designated
> >> > > >>> initializers).
> >> > Mr.
> >> > > @Xiang
> >> > > >>> Xiao  pointed out that "for the
> common
> >> > code
> >> &g

Re: Graduation?

[Alin Jerpelea]

>From the license perspective we should be ready until next weekend

Best regards
Alin

On Wed, 9 Feb 2022, 18:01 Nathan Hartman,  wrote:

> Are we missing any major requirements to graduate to Top Level Project?
>
> If no showstoppers, how does everyone feel about starting the discuss
> thread at the incubator?
>
> Cheers,
> Nathan
>

Re: Graduation?

[Alin Jerpelea]

How long does infra + paperwork take?
When we are ready with everything I will start the 11.0 release cycle

Best regards
Alin

On Wed, 9 Feb 2022, 18:30 Brennan Ashton,  wrote:

> This is taken care of by infra.
>
> Major outstanding bits are around the export control stuff which is mostly
> just paperwork and there apache org has good documentation for.
>
> There is also some code still in the repo with restrictions on use to a
> single microcontroller. That have come up in votes before.
>
> --Brennan
>
> On Wed, Feb 9, 2022, 9:13 AM Alan Carvalho de Assis 
> wrote:
>
> > Nice! I can't get used to this strange github name:
> >
> > https://github.com/apache/incubator-nuttx
> >
> > BTW, is there some way to let github to automatically redirect git
> > clone repo incubator-nuttx to /nuttx after graduation?
> >
> > BR,
> >
> > Alan
> >
> > On 2/9/22, Alin Jerpelea  wrote:
> > > From the license perspective we should be ready until next weekend
> > >
> > > Best regards
> > > Alin
> > >
> > > On Wed, 9 Feb 2022, 18:01 Nathan Hartman, 
> > wrote:
> > >
> > >> Are we missing any major requirements to graduate to Top Level
> Project?
> > >>
> > >> If no showstoppers, how does everyone feel about starting the discuss
> > >> thread at the incubator?
> > >>
> > >> Cheers,
> > >> Nathan
> > >>
> > >
> >
>

Re: Graduation?

[Alin Jerpelea]

my last commits will arrive this week then if there are no other concerns I
would suggest that someone runs FOSSID and verifies independently that I
did not miss anything.

If we all agree that the feedback was addressed I can start a new release
process without the WIP disclaimer

Best regards
Alin


On Mon, 14 Feb 2022, 18:05 Brennan Ashton, 
wrote:

> I really think we need to address the existing feedback from the last two
> releases before we go asking for more.
>
> We also need to go through the process of a release without the WIP
> disclaimer which should also solicit some of the remaining feedback.
>
> --Brennan
>
> On Mon, Feb 14, 2022, 9:00 AM Nathan Hartman 
> wrote:
>
> > On Sat, Feb 12, 2022 at 2:32 AM 张铎(Duo Zhang) 
> > wrote:
> > >
> > > It depends. We need to start a discuss thread on the incubator-general
> > > mailing list to see if IPMC members have any concerns.
> >
> > Hi all,
> >
> > I suggest we go ahead and start that thread. Does anyone need more time
> > first?
> >
> > Cheers,
> > Nathan
> >
>

Re: [DISCUSS]: Self merge and Single company/organization merge gating

[Alin Jerpelea]

Hi Petro,

for me self merge meant also without review from someone else

In the mentioned cases the Author had at least 1 review from someone else
(even from another company)

Best regards
Alin


On Fri, Feb 18, 2022 at 8:52 AM Petro Karashchenko <
petro.karashche...@gmail.com> wrote:

> Hi,
>
> I agree that auto-merge should not be used.
>
> But I disagree that "as it is now since almost all patches follow the
> rule and seldom someone self-merges a patch". Here is a list of
> patches that were self merged last 12 days:
> https://github.com/apache/incubator-nuttx/pull/5474
> https://github.com/apache/incubator-nuttx/pull/5445
> https://github.com/apache/incubator-nuttx/pull/5444
> https://github.com/apache/incubator-nuttx/pull/5428
> https://github.com/apache/incubator-nuttx/pull/5425
> https://github.com/apache/incubator-nuttx/pull/5508
>
> All of the PRs have relatively low complexity and do not touch the
> core functionality so I'm ok with self-merging in such cases.
>
> Best regards,
> Petro
>
> пт, 18 лют. 2022 р. о 08:35 alin.jerpe...@sony.com
>  пише:
> >
> > Hi all
> >
> > In my opinion we should not use the auto merge functionality since most
> of the time there is at least 1 of us active at any time and the amount of
> patches is not comparable to EX: Google.
> >
> > I think that the merge policy is fine as it is now since almost all
> patches follow the rule and seldom someone self-merges a patch.
> >
> > Also we should note that in case some patches land accidentally in the
> master branch we can always revert them if it is necessary
> >
> > Best regards
> > Alin
> >
> > -Original Message-
> > From: David Sidrane 
> > Sent: den 17 februari 2022 22:31
> > To: dev@nuttx.apache.org
> > Subject: RE: [DISCUSS]: Self merge and Single company/organization merge
> gating
> >
> > On Self merge:
> >
> > As Nathan pointed out, it is more about time zones then merge velocity.
> > However, using a backport only methodology requires an upstream merge
> before the work can be backported with least effort and adds a serial
> delay. It would be ideal to reduces the CI quantum delay this as much as we
> can.
> >
> > GH has a setting to merge on successful CI after approval. It is lit by
> the approver. This removes the polling for completion of CI.
> > If this can be configured it reduces the polling for both approver and
> author. If it can not be configured in our repos, then self merge is the
> next best thing.
> >
> > I am not trying to circumvent the review process at all - just remove
> the idle time imposed by the process that is sampling related.
> >
> > > an approval from outside of the company/organization then the author
> > > can do the merge. For complex changes the person outside the
> > > organization should perform the merge even if there are more than 1
> > > approval from inside the company/organization.
> >
> > I agree.
> >
> > David
> >
> > -Original Message-
> > From: Petro Karashchenko 
> > Sent: Thursday, February 17, 2022 1:01 PM
> > To: dev@nuttx.apache.org
> > Subject: Re: [DISCUSS]: Self merge and Single company/organization merge
> gating
> >
> > Hello,
> >
> > Regarding PRs megre by the author: I think that if the changes are
> relatively simple (again that is very subjective, but I hope that people
> with merge rights have more or less the same common sense of
> > it) and there is an approval from outside of the company/organization
> then the author can do the merge. For complex changes the person outside
> the organization should perform the merge even if there are more than 1
> approval from inside the company/organization.
> >
> > In this way reviewers can perform reviews with better quality and if
> someone "forget" to press the "rebase & merge" button because for example
> CI is still running and that is the end of working day, then the author can
> press that button and not do extra tagging in PRs. I vote to make that
> process usable for people and sacrifice bureaucracy in the places where it
> is possible.
> >
> > Best regards,
> > Petro
> >
> > вт, 15 лют. 2022 р. о 18:26 Nathan Hartman 
> пише:
> > >
> > > On Mon, Feb 14, 2022 at 2:01 PM Brennan Ashton
> > >  wrote:
> > > > > Background:
> > > > I am generally opposed to both of these. It is quite rare that we
> > > > need a crazy fast merge turn around on a PR. And if something is
> > > > approved and straight up broken in master that needs to get in then
> > > > I think forgiveness can be used to self merge.
> > > >
> > > >
> > > > I also generally do not have a big issue about people from the same
> > > > company reviewing and merging. I could see the arguments for shared
> > > > code but then I
> > > > think we are nitpicking.   I prefer the velocity with a few oops that
> > > > can
> > > > be reverted along the way if needed.  There is also parts of the
> > > > code base where the best people to review are on the same company.
> > > >
> > > >
> > > > I think most of the concerns here are best addres

[VOTE] Apache NuttX 10.3.0 (incubating) RC0 release

[Alin Jerpelea]

Hello all,


Apache NuttX (Incubating) 10.3.0 RC0 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.3.0-RC0
  Hash for the release incubating-nuttx tag:
c18075779548fcba3f2978689888af8c3b9c959c
  Hash for the release incubating-nuttx-apps tag:
4a2aa6d8cffb6eef45d445ca42a3653f700a2565

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC0/
[2]
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.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

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC0 release

[Alin Jerpelea]

Hi Xiang,

DISCLAIMER-WIP was removed last week from master and release branch and
should not be present anymore

Best regards
Alin





On Wed, 6 Apr 2022, 18:09 Xiang Xiao,  wrote:

> +1 to release
> check with ./tools/checkrelease.sh --release nuttx-10.3.0-RC0 and report
> DISCLAIMER-WIP.not present correctly.
>
> On Fri, Apr 1, 2022 at 9:55 PM Nathan Hartman 
> wrote:
>
> > On Wed, Mar 30, 2022 at 12:50 PM Alin Jerpelea 
> wrote:
> > >
> > > Hello all,
> > >
> > >
> > > Apache NuttX (Incubating) 10.3.0 RC0 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.3.0-RC0
> > >   Hash for the release incubating-nuttx tag:
> > > c18075779548fcba3f2978689888af8c3b9c959c
> > >   Hash for the release incubating-nuttx-apps tag:
> > > 4a2aa6d8cffb6eef45d445ca42a3653f700a2565
> > >
> > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC0/
> > > [2]
> > >
> >
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.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
> >
> >
> > Summary:
> > +1 to release (binding)
> >
> > Per Alan's request for size information [1]:
> >
> > * NuttX-10.3.0-RC0, b-g474e-dpow1:nsh configuration:
> >
> > $ arm-none-eabi-size nuttx
> >textdata bss dec hex filename
> >  117851 6362256  120743   1d7a7 nuttx
> >
> > * For comparison, same configuration on NuttX-10.2.0:
> >
> > $ arm-none-eabi-size nuttx
> >textdata bss dec hex filename
> >  115331 6242500  118455   1ceb7 nuttx
> >
> > Text increases 2520, data increases 12, bss decreases 244.
> >
> >
> From the bloaty output:
>FILE SIZEVM SIZE
>  --  --
>   +4.8% +41.7Ki  [ = ]   0[section .debug_info]
>   +1.5% +2.71Ki  [ = ]   0[section .debug_line]
>   +3.9% +2.33Ki  +3.4% +1.33Ki[157 Others]
>   [NEW]+695  [NEW]+636str_escape
>   +1.9%+604  [ = ]   0[section .debug_frame]
>   [NEW]+556  [NEW]+472cmd_truncate
>   [NEW]+509  [NEW]+468realpath
>   +1.7%+449  [ = ]   0[section .debug_str]
>   +1.5%+416  [ = ]   0[section .symtab]
>   [NEW]+309  [NEW]+244arm_registerdump
>   +2.3%+304  [ = ]   0[section .debug_aranges]
>   [NEW]+219  [NEW]+156arm_dump_stack
>   [NEW]+210  [NEW]+148arm_stackdump
>   [NEW]+208  [NEW]+160getcwd
>   [DEL] -60  [DEL]-204s_last_regs
>  -19.3%-220 -20.9%-220nx_start
>   [DEL]-257  [DEL]-196up_dumpstate
>   [DEL]-304  [DEL]-240up_registerdump
>   [DEL]-380  [DEL]-336mm_memalign
>   -3.4% -2.64Ki  [ = ]   0[Unmapped]
>   -2.5% -3.20Ki  [ = ]   0[section .debug_abbrev]
>   +2.9% +44.1Ki  +2.0% +2.39KiTOTAL
> The major addition come from:
>
>- str_escape comes from:
>https://github.com/apache/incubator-nuttx-apps/pull/861
>- cmd_truncate may related to
>https://github.com/apache/incubator-nuttx-apps/pull/1034
>- realpath and getcwd come from
>https://github.com/apache/incubator-nuttx/pull/5465
>
>
> tl;dr: This release has gotten bigger compared to last 2 releases.
> >
>

[RESULT] [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

[Alin Jerpelea]

Hi,



The vote closes now as over 72hr have passed. The vote PASSES with 4

(+1 non-binding) votes from the PPMC,

4 (+1 binding) vote from the PMC,

1 (+0 non-binding) votes from the developer community,

No further +1, 0 or -1 votes.



The vote thread:

[1]

https://lists.apache.org/thread/21tkdpnjg9y24onplynt2fnl2hcytjk3



I will now bring the vote to gene...@incubator.apache.org to get

approval by the IPMC.

If this vote passes also, the release is accepted and will be

published.



Thanks,

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

[Alin Jerpelea]

I am almost done with the missing files and I will push RC1 today with the
corection

Thanks for your support

Alin

On Tue, 19 Apr 2022, 07:51 张铎(Duo Zhang),  wrote:

> I suggest we analyze these files first, if we should add them to the
> LICENSE files too, we should cancel this vote.
>
> Do not worry, this is our first release without a DISCLAIMER. If we could
> finally publish this release, it is a direct sign that NuttX could graduate
> as a TLP :)
>
> Nathan Hartman  于2022年4月19日周二 02:03写道：
>
> > On Thu, Apr 14, 2022 at 10:39 AM 张铎(Duo Zhang) 
> > wrote:
> > >
> > > Ah, then let me just post them as the content. I've removed several
> files
> > > from the list by the information you provided. And I suggested that
> when
> > > you specify a library, better also provide the place where the related
> > > files are stored. For example, The Rhombus math library, I do not know
> > > which files are for it...
> > >
> > > This is the remaining files. PTAL.
> > >
> > > arch/arm/src/am335x/am335x_lcdc.c
> > > arch/arm/src/armv7-a/cp15_clean_dcache_all.S
> > > arch/arm/src/armv7-a/cp15_flush_dcache_all.S
> > > arch/arm/src/armv7-r/cp15_clean_dcache_all.S
> > > arch/arm/src/armv7-r/cp15_flush_dcache_all.S
> > > arch/arm/src/cxd56xx/hardware/cxd5602_isop.h
> > > arch/arm/src/cxd56xx/hardware/cxd5602_isop_hadc0_highspeed.h
> > > arch/arm/src/imxrt/hardware/rt102x/imxrt102x_xbar.h
> > > arch/arm/src/imxrt/hardware/rt105x/imxrt105x_xbar.h
> > > arch/arm/src/imxrt/hardware/rt106x/imxrt106x_xbar.h
> > > arch/arm/src/lpc2378/lpc23xx_head.S
> > > arch/arm/src/lpc43xx/lpc43_emc.c
> > > arch/arm/src/lpc43xx/lpc43_rtc.h
> > > arch/arm/src/phy62xx/phy62xx_exception.S
> > > arch/arm/src/phy62xx/phy62xx_start.S
> > > arch/arm/src/samd2l2/sam_i2c_master.c
> > > arch/arm/src/samd5e5/sam_i2c_master.c
> > > arch/arm/src/stm32l4/stm32l4_fsmc.h
> > > arch/arm/src/stm32l4/stm32l4_lcd.h
> > > arch/arm/src/tiva/common/tiva_pwm.c
> > > arch/arm/src/tiva/common/tiva_qencoder.c
> > > arch/arm/src/tiva/hardware/lm/lm3s_timer.h
> > > arch/arm/src/tiva/hardware/lm/lm4f_timer.h
> > > arch/arm/src/tiva/hardware/tiva_adc.h
> > > arch/arm/src/tiva/hardware/tiva_epi.h
> > > arch/arm/src/tiva/hardware/tiva_pwm.h
> > > arch/arm/src/tiva/hardware/tiva_qencoder.h
> > > arch/arm/src/tiva/hardware/tm4c/tm4c123_timer.h
> > > arch/arm/src/tiva/hardware/tm4c/tm4c129_timer.h
> > > arch/arm/src/tiva/hardware/tm4c/tm4c_ethernet.h
> > > arch/arm/src/tiva/hardware/tm4c/tm4c_flash.h
> > > arch/arm/src/tiva/tiva_adc.h
> > > arch/arm/src/tiva/tiva_pwm.h
> > > arch/arm/src/tiva/tiva_qencoder.h
> > > arch/or1k/src/mor1kx/hardware/irq.h
> > > arch/xtensa/src/common/xtensa_asm_utils.h
> > > boards/arm/sama5/sama5d4-ek/include/nsh_romfsimg.h
> > > boards/arm/stm32/emw3162/src/stm32_wlan_firmware.c
> > > boards/arm/stm32l4/stm32l476vg-disco/include/nsh_romfsimg.h
> > > boards/arm/stm32l4/stm32l4r9ai-disco/include/nsh_romfsimg.h
> > > boards/sim/sim/sim/include/board.h
> > > boards/sim/sim/sim/src/dummy.c
> > > drivers/leds/ncp5623c.c
> > > drivers/mtd/at24xx.c
> > > drivers/mtd/gd5f.c
> > > drivers/sensors/mlx90614.c
> > > drivers/wireless/ieee80211/bcm43xxx/bcmf_sdio_core.h
> > > drivers/wireless/ieee80211/bcm43xxx/bcmf_sdio_regs.h
> > > include/nuttx/fs/nfs.h
> > > include/nuttx/himem/himem.h
> > > include/nuttx/leds/ncp5623c.h
> > > include/nuttx/net/arp.h
> > > include/nuttx/net/can.h
> > > include/nuttx/net/dns.h
> > > include/nuttx/net/ethernet.h
> > > include/nuttx/net/icmp.h
> > > include/nuttx/net/icmpv6.h
> > > include/nuttx/net/igmp.h
> > > include/nuttx/net/ip.h
> > > include/nuttx/net/netconfig.h
> > > include/nuttx/net/netdev.h
> > > include/nuttx/net/netstats.h
> > > include/nuttx/net/sixlowpan.h
> > > include/nuttx/net/tcp.h
> > > include/nuttx/net/tun.h
> > > include/nuttx/net/udp.h
> > > include/nuttx/wireless/bluetooth/bt_buf.h
> > > include/nuttx/wireless/bluetooth/bt_core.h
> > > include/nuttx/wireless/bluetooth/bt_driver.h
> > > include/nuttx/wireless/bluetooth/bt_gatt.h
> > > include/nuttx/wireless/bluetooth/bt_hci.h
> > > include/nuttx/wireless/bluetooth/bt_ioctl.h
> > > include/nuttx/wireless/bluetooth/bt_null.h
> > > include/nuttx/wireless/bluetooth/bt_uart.h
> > > include/nuttx/wireless/bluetooth/bt_uuid.h
> > > include/nuttx/wireless/ieee80211/ieee80211_cypto.h
> > > include/nuttx/wireless/ieee80211/ieee80211.h
> > > libs/libc/machine/arm/armv7-a/gnu/arch_memcpy.S
> > > libs/libc/machine/arm/armv7-m/gnu/arch_memcpy.S
> > > libs/libc/machine/arm/armv7-r/gnu/arch_memcpy.S
> > > libs/libc/misc/lib_crc16.c
> > > libs/libc/misc/lib_crc32.c
> > > libs/libc/misc/lib_fnmatch.c
> > > libs/libc/misc/lib_ncompress.c
> > > libs/libc/misc/lib_utsname.c
> > > libs/libc/netdb/lib_dns.h
> > > libs/libc/netdb/lib_dnsquery.c
> > > libs/libc/net/lib_addrconfig.c
> > > libs/libc/stdlib/lib_strtod.c
> > > libs/libc/stdlib/lib_strtof.c
> > > libs/libc/stdlib/lib_strtold.c
> > > libs/libc/stdlib/lib_wctomb.c
> > > libs/libc/string/lib_vikmemcpy.c
> > > net/arp/arp

[VOTE] Apache NuttX 10.3.0 (incubating) RC1 release

[Alin Jerpelea]

Hello all,


Apache NuttX (Incubating) 10.3.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.3.0-RC1
  Hash for the release incubating-nuttx tag:
2e3c217d103f9c98dc3e4c6f02ba87e6e8b719f0
  Hash for the release incubating-nuttx-apps tag:
ecd8a9722f9da777829ed6f28998311f1664b278

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC1/
[2]
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC1/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 10.3.0 (incubating) RC2 release

[Alin Jerpelea]

Hello all,


Apache NuttX (Incubating) 10.3.0 RC2 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.3.0-RC2
  Hash for the release incubating-nuttx tag:
ec8fa7d2bfd649d8848448243744e30c96467ff2
  Hash for the release incubating-nuttx-apps tag:
ecd8a9722f9da777829ed6f28998311f1664b278

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC2/
[2]
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC2/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC1 release

[Alin Jerpelea]

VOTING CLOSED!



I will create a new vote for 10.3-0 RC2 with the reported issues fixed



Thanks for all your support

Alin

On Wed, May 4, 2022 at 8:30 AM alin.jerpe...@sony.com <
alin.jerpe...@sony.com> wrote:

> Hi Masayuki -san
>
> Are you able to cherry-pick and test the patches on the real HW ?
>
> Thanks
> Alin
>
>
> -Original Message-
> From: Masayuki Ishikawa 
> Sent: den 3 maj 2022 16:17
> To: dev@nuttx.apache.org
> Subject: Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC1 release
>
> -1
>
> sabre-6quad:smp (real hardware) does not boot.
> I think some armv7-a-related PRs need to be merged.
>
> On Wed, Apr 27, 2022 at 5:01 PM Alin Jerpelea  wrote:
>
> > Hello all,
> >
> >
> > Apache NuttX (Incubating) 10.3.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.3.0-RC1
> >   Hash for the release incubating-nuttx tag:
> > 2e3c217d103f9c98dc3e4c6f02ba87e6e8b719f0
> >   Hash for the release incubating-nuttx-apps tag:
> > ecd8a9722f9da777829ed6f28998311f1664b278
> >
> > [1]
> > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc
> > ubator/nuttx/10.3.0-RC1/__;!!JmoZiZGBv3RvKRSx!4aququvO7zQseiusM3fVPWZq
> > Hup5x8YDb2G67QRh0r-6yhO42lpQspOum_H5U2ckeBXP6zVNIpmNrW6cKYZ482YHbNff$
> > [2]
> >
> > https://urldefense.com/v3/__https://raw.githubusercontent.com/apache/i
> > ncubator-nuttx/nuttx-10.3.0-RC1/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!4aqu
> > quvO7zQseiusM3fVPWZqHup5x8YDb2G67QRh0r-6yhO42lpQspOum_H5U2ckeBXP6zVNIp
> > mNrW6cKYZ48-I3p9r2$ [3]
> > https://urldefense.com/v3/__https://www.apache.org/dev/release.html*ap
> > proving-a-release__;Iw!!JmoZiZGBv3RvKRSx!4aququvO7zQseiusM3fVPWZqHup5x
> > 8YDb2G67QRh0r-6yhO42lpQspOum_H5U2ckeBXP6zVNIpmNrW6cKYZ484QkBmjj$
> > [4]
> >
> > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/displa
> > y/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!4aququvO7
> > zQseiusM3fVPWZqHup5x8YDb2G67QRh0r-6yhO42lpQspOum_H5U2ckeBXP6zVNIpmNrW6
> > cKYZ48y7wfpdl$
> >
>

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]

[Alin Jerpelea]

Hi Duo Zhang,

which are the remaining License issues?
I will add back the keys to the key file ASAP.

Thanks
Alin


On Sun, 5 Jun 2022, 10:45 张铎(Duo Zhang),  wrote:

> -- Forwarded message -
> 发件人： 张铎(Duo Zhang) 
> Date: 2022年6月5日周日 16:36
> Subject: Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]
> To: 
>
>
> I could verify the gpg signature
>
> gpg --verify apache-nuttx-10.3.0-incubating.tar.gz.asc
> > gpg: 假定被签名的数据在‘apache-nuttx-10.3.0-incubating.tar.gz’
> > gpg: 签名建立于 2022年05月05日 星期四 15时40分00秒 CST
> > gpg:使用 RSA 密钥 FAFEEA08ABE09A8F060D984CA57CE1279F1E7328
> > gpg: 完好的签名，来自于 “Alin Jerpelea (CODE SIGNING KEY) ”
> > [未知]
> > gpg: 警告：此密钥未被受信任签名认证！
> > gpg:  没有证据表明此签名属于其声称的所有者。
> > 主密钥指纹： FAFE EA08 ABE0 9A8F 060D  984C A57C E127 9F1E 7328
>
>
> But the key FAFEEA08ABE09A8F060D984CA57CE1279F1E7328 is not in the current
> KEYS file. I guess it was in the KEYS file in the past so I imported in the
> past.
>
> Please update the KEYS file to add it back Alin, usually we should not
> delete keys from the KEYS file, especially when we are still using the key
> to sign artifacts.
>
> And on the DISCLAIMER, I used to think if we can fix all the license
> problems then we can remove it. Will tell the community to add it back, and
> remove it once NuttX becomes a TLP.
>
> Thanks Justin.
>
> Justin Mclean  于2022年6月5日周日 10:16写道：
>
> > Hi,
> >
> > Sorry for the delay in checking the but I am also -1 binding as I can’t
> > verify the signature and teh disclaimer is missing.
> >
> > I checked:
> > - incubating in name
> > - while sha512 is correct it looks like the signature is missing from the
> > KEYS file
> > - DISCLAIMER is missing
> > - LICENSE looks fine (but I didn’t;t do a comprehensive check)
> > - NOTICE need it’s year updated
> > - No unexpected binary files
> > - ASF files have ASF headers
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]

[Alin Jerpelea]

Hi Justin,

I resigned the release with the new key and uploaded it so that the release
and the key match

Thanks
Alin

On Sun, 5 Jun 2022, 10:45 张铎(Duo Zhang),  wrote:

> -- Forwarded message -
> 发件人： 张铎(Duo Zhang) 
> Date: 2022年6月5日周日 16:36
> Subject: Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]
> To: 
>
>
> I could verify the gpg signature
>
> gpg --verify apache-nuttx-10.3.0-incubating.tar.gz.asc
> > gpg: 假定被签名的数据在‘apache-nuttx-10.3.0-incubating.tar.gz’
> > gpg: 签名建立于 2022年05月05日 星期四 15时40分00秒 CST
> > gpg:使用 RSA 密钥 FAFEEA08ABE09A8F060D984CA57CE1279F1E7328
> > gpg: 完好的签名，来自于 “Alin Jerpelea (CODE SIGNING KEY) ”
> > [未知]
> > gpg: 警告：此密钥未被受信任签名认证！
> > gpg:  没有证据表明此签名属于其声称的所有者。
> > 主密钥指纹： FAFE EA08 ABE0 9A8F 060D  984C A57C E127 9F1E 7328
>
>
> But the key FAFEEA08ABE09A8F060D984CA57CE1279F1E7328 is not in the current
> KEYS file. I guess it was in the KEYS file in the past so I imported in the
> past.
>
> Please update the KEYS file to add it back Alin, usually we should not
> delete keys from the KEYS file, especially when we are still using the key
> to sign artifacts.
>
> And on the DISCLAIMER, I used to think if we can fix all the license
> problems then we can remove it. Will tell the community to add it back, and
> remove it once NuttX becomes a TLP.
>
> Thanks Justin.
>
> Justin Mclean  于2022年6月5日周日 10:16写道：
>
> > Hi,
> >
> > Sorry for the delay in checking the but I am also -1 binding as I can’t
> > verify the signature and teh disclaimer is missing.
> >
> > I checked:
> > - incubating in name
> > - while sha512 is correct it looks like the signature is missing from the
> > KEYS file
> > - DISCLAIMER is missing
> > - LICENSE looks fine (but I didn’t;t do a comprehensive check)
> > - NOTICE need it’s year updated
> > - No unexpected binary files
> > - ASF files have ASF headers
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]

[Alin Jerpelea]

 ok. What else is needed for graduation?
Should I add the DISCLAIMER back and start the RC3 vote?
Thanks
Alin

On Sun, 5 Jun 2022, 14:58 张铎(Duo Zhang),  wrote:

> Seems the incubating project must have a DISCLAIMER file, which indicates
> that it is still 'incubating', and the ASF does not guarantee that it has
> no license issues. Not a big problem, we can remove it after we graduate as
> a TLP.
>
> Alin Jerpelea  于2022年6月5日周日 17:13写道：
>
> > Hi Duo Zhang,
> >
> > which are the remaining License issues?
> > I will add back the keys to the key file ASAP.
> >
> > Thanks
> > Alin
> >
> >
> > On Sun, 5 Jun 2022, 10:45 张铎(Duo Zhang),  wrote:
> >
> > > -- Forwarded message -
> > > 发件人： 张铎(Duo Zhang) 
> > > Date: 2022年6月5日周日 16:36
> > > Subject: Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC2]
> > > To: 
> > >
> > >
> > > I could verify the gpg signature
> > >
> > > gpg --verify apache-nuttx-10.3.0-incubating.tar.gz.asc
> > > > gpg: 假定被签名的数据在‘apache-nuttx-10.3.0-incubating.tar.gz’
> > > > gpg: 签名建立于 2022年05月05日 星期四 15时40分00秒 CST
> > > > gpg:使用 RSA 密钥
> FAFEEA08ABE09A8F060D984CA57CE1279F1E7328
> > > > gpg: 完好的签名，来自于 “Alin Jerpelea (CODE SIGNING KEY) <
> jerpe...@apache.org
> > >”
> > > > [未知]
> > > > gpg: 警告：此密钥未被受信任签名认证！
> > > > gpg:  没有证据表明此签名属于其声称的所有者。
> > > > 主密钥指纹： FAFE EA08 ABE0 9A8F 060D  984C A57C E127 9F1E 7328
> > >
> > >
> > > But the key FAFEEA08ABE09A8F060D984CA57CE1279F1E7328 is not in the
> > current
> > > KEYS file. I guess it was in the KEYS file in the past so I imported in
> > the
> > > past.
> > >
> > > Please update the KEYS file to add it back Alin, usually we should not
> > > delete keys from the KEYS file, especially when we are still using the
> > key
> > > to sign artifacts.
> > >
> > > And on the DISCLAIMER, I used to think if we can fix all the license
> > > problems then we can remove it. Will tell the community to add it back,
> > and
> > > remove it once NuttX becomes a TLP.
> > >
> > > Thanks Justin.
> > >
> > > Justin Mclean  于2022年6月5日周日 10:16写道：
> > >
> > > > Hi,
> > > >
> > > > Sorry for the delay in checking the but I am also -1 binding as I
> can’t
> > > > verify the signature and teh disclaimer is missing.
> > > >
> > > > I checked:
> > > > - incubating in name
> > > > - while sha512 is correct it looks like the signature is missing from
> > the
> > > > KEYS file
> > > > - DISCLAIMER is missing
> > > > - LICENSE looks fine (but I didn’t;t do a comprehensive check)
> > > > - NOTICE need it’s year updated
> > > > - No unexpected binary files
> > > > - ASF files have ASF headers
> > > >
> > > > Kind Regards,
> > > > Justin
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

[VOTE] Apache NuttX 10.3.0 (incubating) RC3 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 10.3.0 RC3 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.3.0-RC3
  Hash for the release incubating-nuttx tag:
c4952b7788e6f5891421a24e27371373c25be7a5
  Hash for the release incubating-nuttx-apps tag:
bc6f5d6fd775b8ca65870a9ea5dc02ac90a86901

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC3/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC3/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC3 release

[Alin Jerpelea]

Thanks for clearing out the confusion
I will update the release with the needed changes and call for a vote ASAP

Best Regards
Alin

On Tue, 7 Jun 2022, 09:49 Abdelatif Guettouche, <
abdelatif.guettou...@gmail.com> wrote:

> Hi,
> Regarding the disclaimer, the idea was to remove the WIP part _only_,
> to end up with a standard disclaimer file and not a WIP disclaimer
> file. [1]
> I believe we are required to make at least one non WIP release to be
> eligible for graduation and given all the work on licensing that has
> been done, we can drop the WIP part.
>
> 1. https://incubator.apache.org/policy/incubation.html#disclaimers
>
> On Tue, Jun 7, 2022 at 9:38 AM Alin Jerpelea  wrote:
> >
> > Hello all,
> > Apache NuttX (Incubating) 10.3.0 RC3 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.3.0-RC3
> >   Hash for the release incubating-nuttx tag:
> > c4952b7788e6f5891421a24e27371373c25be7a5
> >   Hash for the release incubating-nuttx-apps tag:
> > bc6f5d6fd775b8ca65870a9ea5dc02ac90a86901
> >
> > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC3/
> > [2]
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC3/ReleaseNotes
> > [3] https://www.apache.org/dev/release.html#approving-a-release
> > [4]
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
>

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC3 release

[Alin Jerpelea]

Hi all,

The RC3 vote is canceled

Reason:
Fix DISCLAIMER
add PR#5930

Thanks for providing feedback

I will start a new vote for RC4

Best regards
Alin


On Tue, Jun 7, 2022 at 10:41 AM fft  wrote:

> Hi
> I notice that 10.3.0 RC3 doesn't include PR#5930, so anyone who use segger
> RTT in armv7m, there will a compile error of can't find the
> SEGGER_RTT_Conf.h
> May this be included？
>
>
>
>
> Best Regards
> zouboan
> ------ Original --
> From:  "Alin Jerpelea" Date:  Tue, Jun 7, 2022 03:38 PM
> To:  "dev"
> Subject:  [VOTE] Apache NuttX 10.3.0 (incubating) RC3 release
>
>  
>
> Hello all,
> Apache NuttX (Incubating) 10.3.0 RC3 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.3.0-RC3
>   Hash for the release incubating-nuttx tag:
> c4952b7788e6f5891421a24e27371373c25be7a5
>   Hash for the release incubating-nuttx-apps tag:
> bc6f5d6fd775b8ca65870a9ea5dc02ac90a86901
>
> [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC3/
> [2]
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC3/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 10.3.0 (incubating) RC4 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 10.3.0 RC4 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.3.0-RC4
  Hash for the release incubating-nuttx tag:
3fb5737958000d6e786a885af1a576e4d7bd5ada
  Hash for the release incubating-nuttx-apps tag:
10c75df01cfb65d3d865313ebc03af6aec8505e5

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.3.0-RC4/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.3.0-RC4/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

[RESULT] Release Apache NuttX (Incubating) 10.3.0 [RC4]

[Alin Jerpelea]

Hi,

The vote closes now as over 72hr have passed. The vote PASSES with 3

2 (+1 non-binding) votes from the PPMC,
1 (+1 binding) vote from the IPMC,
0 (+1 non-binding) votes from the developer community, No further +1, 0 or
-1 votes.

The vote thread:
[1]
https://lists.apache.org/thread/ryjztshx8olc4gdkt3ryfqjrsghp64h3

I will now bring the vote to gene...@incubator.apache.org to get approval
by the IPMC.
If this vote passes also, the release is accepted and will be published.

Thanks,
Alin Jerpelea

[ANNOUNCE] Apache NuttX 10.3.0-incubating released

[Alin Jerpelea]

The Apache NuttX (incubating) project team is proud to announce
Apache NuttX 10.3.0-incubating has been released.

The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/10.3.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: [DISCUSS] Graduate NuttX as TLP

[Alin Jerpelea]

+1 for graduation
and +1 for the joke idea

Thanks
Alin

On Mon, 27 Jun 2022, 19:18 Alan Carvalho de Assis, 
wrote:

> Hahaha, I liked that joke! Alin, please use this same joke in the NuttX
> Online Workshop thread!
>
> +1 to graduation!
>
> I don't know you guys but I hate this incubator-nuttx and
> incubator-nuttx-apps repositories names.
>
> I hope we get github.com/apache/nuttx and github.com/apache/apps soon
> (hope
> they accept we use this /apps name, will make our users life easier!)
>
> BR,
>
> Alan
>
> On Monday, June 27, 2022, Nathan Hartman  wrote:
>
> > On Fri, Jun 24, 2022 at 12:46 PM Nathan Hartman
> >  wrote:
> > >
> > > Hi folks,
> > >
> > > It's time to start the [DISCUSS] thread about GRADUATION!
> > >
> > > Project Highlights Since Incubation:
> > >
> > > * Incubating since 2019-12-09
> > > * New website, nuttx.apache.org
> > > * Shipped 8 releases under the ASF Incubator, including our first
> > > non-WIP release
> > > * Merged more than 7000 PRs across incubator-nuttx and
> > incubator-nuttx-apps
> > > * More than 1000 stars on GitHub
> > > * More than 500 forks on GitHub
> > > * More than 250 subscribers to dev@nuttx.apache.org
> > > * 9th most active Apache project of 2021 by number of commits [1]
> > > * 5 mentors
> > > * 17 PPMC members
> > > * 25 committers
> > > * 75 ICLAs
> > > * 2 CCLAs
> > > * 21 SGAs
> > > * 2 release managers
> > > * 2 NuttX online workshops
> > > * And much, much more
> > >
> > > Let's go through the checklist [2], discuss any remaining open issues,
> > > and get this process going!
> > >
> > > References:
> > > [1] https://thestack.technology/top-apache-projects-in-2021-
> > from-superset-to-nuttx/
> > > [2] https://incubator.apache.org/guides/graduation.html#before_
> > you_graduate
> > >
> > > Cheers,
> > > Nathan
> >
> > Ping... Don't all reply at once!
> >
> > Cheers,
> > Nathan
> >
>

[VOTE] Apache NuttX 10.4.0 (incubating) RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 10.4.0 RC0 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.4.0-RC0
  Hash for the release incubating-nuttx tag:
dd718e78f70f9350ac648067509672c5051841b9
  Hash for the release incubating-nuttx-apps tag:
8b43f9f9ca30f44c1cccae9a9078d5d45b776d35

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.4.0-RC0/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.4.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

Re: [VOTE] Apache NuttX 10.4.0 (incubating) RC0 release

[Alin Jerpelea]

@Alan Carvalho de Assis   please confirm that works
after revert

On Thu, 11 Aug 2022, 20:22 Petro Karashchenko, 
wrote:

> Hello Alan,
>
> Seems that the root cause is my change
> https://github.com/apache/incubator-nuttx-apps/pull/1097
>
> I think that all previously generated passwords need to be re-generated.
>
> Best regards,
> Petro
>
> On Thu, Aug 11, 2022, 8:49 PM Alan Carvalho de Assis 
> wrote:
>
> > Alin,
> >
> > I want to redraw my vote, I found the first regression, so my vote is:
> >
> > -1
> >
> > Seems like the console login is not working, I'm using user: admin and
> > password: Administrator
> >
> > $ ./tools/configure.sh sim:nsh
> >
> > $ make -j
> >
> > $ ./nuttx
> > login: admin
> > password:
> > Invalid username or password
> > login: admin
> > password:
> > Invalid username or password
> > login: admin
> > password:
> > Invalid username or password
> > Login failed!
> >
> > I double checked the /etc/passwd file and it is correct:
> >
> > nsh> cat /etc/passwd
> > admin:8Tv+Hbmr3pLddSjtzL0kwC:0:0:/
> >
> > Please help me to find the offending commit.
> >
> > BR,
> >
> > Alan
> >
> > On 8/8/22, Alin Jerpelea  wrote:
> > > Hello all,
> > > Apache NuttX (Incubating) 10.4.0 RC0 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.4.0-RC0
> > >   Hash for the release incubating-nuttx tag:
> > > dd718e78f70f9350ac648067509672c5051841b9
> > >   Hash for the release incubating-nuttx-apps tag:
> > > 8b43f9f9ca30f44c1cccae9a9078d5d45b776d35
> > >
> > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.4.0-RC0/
> > > [2]
> >
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.4.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 11.0.0 (incubating) RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 11.0.0 RC0 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,


SCM Information:
  Release tag: nuttx-11.0.0-RC0
  Hash for the release incubating-nuttx tag:
53800a86574b3d8b144bd3b6630cb16b8e1d0f92
  Hash for the release incubating-nuttx-apps tag:
8b43f9f9ca30f44c1cccae9a9078d5d45b776d35

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC0/
[2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-11.0.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

Re: Article: PinePhone boots NuttX

[Alin Jerpelea]

Nice!

On Sat, 27 Aug 2022, 19:06 Tomek CEDRO,  wrote:

> wow! respect!! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>
> On Sat, Aug 27, 2022, 13:25 Lee, Lup Yuen  wrote:
>
> > NuttX now boots on Pine64's PinePhone! (Arm Cortex-A53) This article
> > explains the changes that I made...
> >
> > https://lupyuen.github.io/articles/uboot
> >
> > Lup
> >
>

Re: Reevaluate the C89 Requirement

[Alin Jerpelea]

-1 for the same reasons

On Tue, 30 Aug 2022, 11:30 Sebastien Lorquet,  wrote:

> Hi,
>
> That would be -1 for me too.
>
> Reason 1 from Nathan could change my vote.
>
> But reason 2 would be a shame. We have one of the few a RTOS that
> support CPUs outside ARM.
>
>
> TBH, there is no solid technical reason to change this rule. Most of the
> things mentioned in this comment are syntactic sugar that can be
> supported with macros.
>
>
> Sebastien
>
> Le 30/08/2022 à 03:18, Nathan Hartman a écrit :
> > On Mon, Aug 29, 2022 at 7:54 PM Alan Rosenthal  >
> > wrote:
> >
> >> Hi!
> >>
> >> What needs to be done to open the discussion to consider changing the
> >> rules?
> >>
> >> Also please see a very detailed comment on the github issue here by
> >> @robertlipe:
> >>
> https://github.com/apache/incubator-nuttx/issues/6896#issuecomment-1227971503
> >>
> >
> > Basically what Greg said: motivate someone of the PPMC to call a vote.
> >
> > Just FYI, based on what Byron points out with regard to the Zilog
> families
> > needing C89 (and possibly other archs that weren't mentioned), I would
> > probably vote -1 unless either:
> >
> > 1) there is a toolchain, which is complete (not "experimental") that
> > supports these platforms, or:
> >
> > 2) someone can convince me that no one cares about these architectures
> > anymore, such as if it's shown that NuttX already contains significant
> > breakage on these platforms that prevents them from working anyway, no
> one
> > has complained, and it has gone unfixed for several years
> >
> > If 1 or 2 (or both) I'm okay with it. But if changing the rules will
> leave
> > users in the dust, then I'm not okay with it.
> >
> > Just my thoughts... I'll be glad to hear the thoughts of others.
> >
> > Cheers,
> > Nathan
> >
>

[VOTE] Apache NuttX 11.0.0 (incubating) RC1 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 11.0.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-11.0.0-RC1
  Hash for the release incubating-nuttx tag:
6feb2a1f4196e361b7aa8e209534a158cd14c833
  Hash for the release incubating-nuttx-apps tag:
8b43f9f9ca30f44c1cccae9a9078d5d45b776d35

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC1/
[2] 
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-11.0.0-RC1/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Subject: [VOTE] Apache NuttX 11.0.0 (incubating) RC2 release

[Alin Jerpelea]

Hello all,
Apache NuttX (Incubating) 11.0.0 RC2 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-11.0.0-RC2
  Hash for the release incubating-nuttx tag:
d32555f3e0492b8f4caeb407db55de23322724ef
  Hash for the release incubating-nuttx-apps tag:
8b43f9f9ca30f44c1cccae9a9078d5d45b776d35

[1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/
[2] 
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-11.0.0-RC2/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Re: [VOTE] Apache NuttX 11.0.0 (incubating) RC1 release

[Alin Jerpelea]

Hi,

The vote closes now as over 72hr have passed. The vote DOES NOT PASS !

2 (+1 non binding) vote from the PMC,
2 (-1 non-binding) votes from the developer community,
No further +1, 0 or -1 votes.


I will created RC2 with the proposed changes and open a new vote

Release Manager,
Alin Jerpelea


On Thu, Sep 8, 2022 at 5:17 PM Gustavo Henrique Nihei 
wrote:

> -1
>
> FPU Test in ostest app fails on ESP32 and ESP32-S3. We need to include
> fixes from the following PRs:
> https://github.com/apache/incubator-nuttx/pull/6917
> https://github.com/apache/incubator-nuttx/pull/6924
>
> Furthermore, it would be nice to include these other fixes to ESP32-S2 and
> ESP32-S3 chips:
> https://github.com/apache/incubator-nuttx/pull/6916
> https://github.com/apache/incubator-nuttx/pull/6937
> https://github.com/apache/incubator-nuttx/pull/6990
>
>
> On Thu, Sep 8, 2022 at 11:47 AM Alan Carvalho de Assis 
> wrote:
>
> > +1
> >
> > Please find below important information for analysis/comparison:
> >
> > ESP32-DEVKITC:
> > ==
> >
> > Compiler info
> > -
> >
> > $ xtensa-esp32-elf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=xtensa-esp32-elf-gcc
> >
> >
> COLLECT_LTO_WRAPPER=/usr/local/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
> >
> >
> --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-patch3'
> > --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections
> > --disable-libgomp --disable-libmudflap --disable-libmpx
> > --disable-libssp --disable-libquadmath --disable-libquadmath-support
> > --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-patch3)
> >
> >
> > Configure
> > -
> >
> > $ ./tools/configure.sh esp32-devkitc:nsh
> >
> > Compile/Flash
> > -
> >
> > $ make flash -j ESPTOOL_PORT=/dev/ttyUSB0
> >
> >
> > ELF Size
> > 
> >
> > $ xtensa-esp32-elf-size nuttx
> >textdata bss dec hex filename
> >   73927 2364696   78859   1340b nuttx
> >
> >
> > NSH Free
> > 
> >
> > nsh> free
> >total   used   freelargest  nused  nfree
> > Umem: 327648   5824 321824 190160 31  3
> >
> >
> >
> > ESP32C3-DEVKIT:
> > ==
> >
> > Compiler info
> > -
> >
> > $ riscv64-unknown-elf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=riscv64-unknown-elf-gcc
> >
> >
> COLLECT_LTO_WRAPPER=/usr/local/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
> > Target: riscv64-unknown-elf
> > Configured with:
> >
> >
> /scratch/jenkins/workspace/tpp-freedom-tools/tpp03--build-binary-packages--parameterized/obj/x86_64-linux-ubuntu14/build/riscv64-unknown-elf-gcc/riscv-gcc/configure
> > --target=riscv64-unknown-elf --host=x86_64-linux-gnu
> >
> >
> --prefix=/scratch/jenkins/workspace/tpp-freedom-tools/tpp03--build-binary-packages--parameterized/obj/x86_64-linux-ubuntu14/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-linux-ubuntu14
> > --with-pkgversion='SiFive GCC-Metal 10.2.0-2020.12.8'
> > --with-bugurl=https://github.com/sifive/freedom-tools/issues
> > --disable-shared --disable-threads --enable-languages=c,c++
> > --enable-tls --with-newlib
> >
> >
> --with-sysroot=/scratch/jenkins/workspace/tpp-freedom-tools/tpp03--build-binary-packages--

[RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]

[Alin Jerpelea]

Hi,

The vote closes now as over 72hr have passed. The vote PASSES with 3
(+3 non-binding) votes from the PPMC,
0 (+1 binding) vote from the IPMC,
3 (+0 non-binding) votes from the developer community,
No further +1, 0 or -1 votes.

The vote thread:
[1]https://lists.apache.org/thread/rv9pf8gtbcq4zjnydv2h2lsymszzb33f

I will now bring the vote to gene...@incubator.apache.org to get
approval by the IPMC.
If this vote passes also, the release is accepted and will be
published.

Thanks,
Alin Jerpelea

Re: NuttX International Workshop 2022: will start in less than 14h

[Alin Jerpelea]

Hi Greg,

we will send each day (today and tomorrow) links for the speakers and you

The links for attendees will be posted on https://nuttx.events/

Best Regards
Alin



On Sat, 24 Sept 2022, 02:29 spudaneco,  wrote:

> Hi, Alan,Question... Are there instruction anywhere for connecting to the
> presentations?GregSent from my Galaxy
>  Original message From: "Alan C. Assis" 
> Date: 9/23/22  3:07 PM  (GMT-06:00) To: dev 
> Subject: NuttX International Workshop 2022: will start in less than 14h Hi
> Everyone,We are looking forward to see you tomorrow in the NuttX
> Workshop.The schedule with all the presentations is already available:
> https://nuttx.events/BR,Alan

Re: NuttX International Workshop 2022: will start in less than 14h

[Alin Jerpelea]

Hi ,

the event starts at 11:00 GMT and the links will be shared 30 minutes before

thanks for your patience

Best Regards
Alin

On Sat, 24 Sept 2022, 10:42 Tomek CEDRO,  wrote:

> still no links?
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>
> On Sat, Sep 24, 2022, 08:03 Alin Jerpelea  wrote:
>
> > Hi Greg,
> >
> > we will send each day (today and tomorrow) links for the speakers and you
> >
> > The links for attendees will be posted on https://nuttx.events/
> >
> > Best Regards
> > Alin
> >
> >
> >
> > On Sat, 24 Sept 2022, 02:29 spudaneco,  wrote:
> >
> > > Hi, Alan,Question... Are there instruction anywhere for connecting to
> the
> > > presentations?GregSent from my Galaxy
> > >  Original message From: "Alan C. Assis" <
> > acas...@gmail.com>
> > > Date: 9/23/22  3:07 PM  (GMT-06:00) To: dev 
> > > Subject: NuttX International Workshop 2022: will start in less than 14h
> > Hi
> > > Everyone,We are looking forward to see you tomorrow in the NuttX
> > > Workshop.The schedule with all the presentations is already available:
> > > https://nuttx.events/BR,Alan
> >
>

Re: Unicode characters in codebase.

[Alin Jerpelea]

Let's remove them!

Thanks for looking into this issue

Best Regards
Alin

On Mon, 10 Oct 2022, 17:25 Alan C. Assis,  wrote:

> Agree! It is better to avoid it.
>
> On 10/10/22, Fotis Panagiotopoulos  wrote:
> > Hello!
> >
> > A few weeks ago I had some problems with a static analysis tool that
> > couldn't parse NuttX code, due to non-Unicode characters. I provided a
> > couple of PRs and fixed the issues, but it got me thinking...
> >
> > Do we really need Unicode characters within the codebase?
> >
> > I can only think of problems with this, from missing glyphs from fonts,
> to
> > difficulties in search...
> > I don't see any value in writing μs instead of us, or I²C instead of I2C.
> >
> > What do you think?
> > Shall we allow such characters, or enforce ASCII-only characters in the
> > codebase?
> >
>

[ANNOUNCE] Apache NuttX 11.0.0-incubating released

[Alin Jerpelea]

The Apache NuttX (incubating) project team is proud to announce
Apache NuttX 11.0.0-incubating has been released.

The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/11.0.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: [DISCUSS] Graduate NuttX as TLP

[Alin Jerpelea]

+1
I think that we are ready to graduate


Best regards
Alin

On Wed, 19 Oct 2022, 06:16 Tomek CEDRO,  wrote:

> Just my vote for the path names:
> apache/nuttx_rtos
> apache/nuttx_apps
>
> Looks safe and self-explanatory :-)
>
> If clone to nuttx_rtos.git/ and nuttx_apps.git/ would be also acceptable
> that would be perfect (and marked there is a git repo inside).
>
> Thank You and Good Luck! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: [VOTE] Apache NuttX Community Graduation

[Alin Jerpelea]

+1: Apache NuttX is ready to graduate to TLP
Best Regards
Alin

On Fri, 21 Oct 2022, 14:53 Tomek CEDRO,  wrote:

> +1: Apache NuttX is ready to graduate to TLP ! :-)
> Tomek CEDRO
>
>
> On Fri, Oct 21, 2022 at 2:47 PM Nathan Hartman 
> wrote:
> >
> > Dear Apache NuttX Community,
> >
> > Following the [DISCUSS] thread which has gone 72 hours without any
> > further issues raised [1]:
> >
> > This is a call to VOTE on Graduation of Apache NuttX from the
> > Incubator to Top-Level Project (TLP).
> >
> > Please vote:
> >
> > [ ] +1: Apache NuttX is ready to graduate to TLP
> > [ ]  0: No opinion
> > [ ] -1: Apache NuttX is NOT ready to graduate; please state reason(s)
> >
> > If this community vote passes, we will proceed to the next steps. The
> > graduation process is documented at [2]. The vote will remain open for
> > at least 72 hours. A minimum of 3 binding +1 votes and more binding +1
> > than binding -1 are required to pass. The ASF requirements for voting
> > can be found at [3].
> >
> > Project Highlights Since Incubation:
> > * Incubating since 2019-12-09
> > * Website migrated to nuttx.apache.org
> > * Shipped 9 releases under the ASF Incubator
> > * Merged 8000 PRs across incubator-nuttx and incubator-nuttx-apps
> > * More than 1000 stars on GitHub
> > * More than 500 forks on GitHub
> > * More than 250 subscribers to dev@nuttx.apache.org
> > * In Top 10 Apache projects of 2021 by number of commits [4]
> > * 5 mentors
> > * 18 PPMC members
> > * 26 committers
> > * 75 ICLAs
> > * 2 CCLAs
> > * 21 SGAs
> > * 2 release managers
> > * 3 NuttX online workshops
> > * And much, much more
> >
> > Let me express a big ***THANK YOU*** to everyone for helping make this
> > possible!
> >
> > [1] https://lists.apache.org/thread/vpj21ofyxmjs528n3b9s72wozh9hjz8f
> >
> > [2]
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_top_level_project
> >
> > [3] https://www.apache.org/foundation/voting.html
> >
> > [4]
> https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/
> >
> > Cheers,
> > Nathan Hartman
>
>
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: [DISCUSS] NuttX graduation: Draft Resolution

[Alin Jerpelea]

If none has a better idea I can step in

Best Regards
Alin

On Fri, 28 Oct 2022, 06:35 Nathan Hartman,  wrote:

> Ping... Folks, we need to choose a Vice President for the proposed
> Apache NuttX TLP.
>
>
> On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman 
> wrote:
> >
> > Dear NuttX community,
> >
> > As our community VOTE [1] for graduation to Top Level Project has
> > PASSED [2], the next steps are:
> >
> > (1) Draft our Charter/Resolution
> > (2) Decide members of the initial Project Management Committee (PMC)
> > (3) Choose the 1st Vice President of the proposed Apache NuttX PMC
> >
> > Please participate so we can get this done efficiently!
> >
> > Regarding item #1, below please find a 1st Draft Resolution for review
> > and discussion -- this draft was generated by Whimsy (there's a button
> > at the bottom of our podling page [3] to draft the resolution). Please
> > read it anyway and provide feedback!!!
> >
> > Regarding item #2, currently the draft resolution lists all members of
> > the Apache NuttX (Incubating) PPMC to become members of the proposed
> > Apache NuttX PMC. If anyone feels there should be changes, please let
> > us know.
> >
> > Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
> > where the name of the proposed Vice President should be written. We
> > need to decide who that will be. The Vice President reports to the
> > board 4 times each year, similarly to how we have been reporting to
> > the Incubator PMC (IPMC), but there are no mentors who need to sign
> > off on it. Speak up if you're interested in being the Vice President
> > of Apache NuttX!
> >
> > 1st draft of our Resolution:
> >
> > [[[
> >
> > Establish the Apache NuttX Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to
> > establish a Project Management Committee charged with the creation and
> > maintenance of open-source software, for distribution at no charge to
> > the public, related to a mature, real-time embedded operating system
> > (RTOS).
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache NuttX Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache NuttX Project be and hereby is responsible
> > for the creation and maintenance of software related to a mature, real-
> > time embedded operating system (RTOS); and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache NuttX" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache NuttX
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache NuttX
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache NuttX Project:
> >
> >  * Abdelatif Guettouche   
> >  * Alan Carvalho de Assis 
> >  * Alin Jerpelea  
> >  * Anthony Merlino
> >  * Brennan Ashton 
> >  * David Sidrane  
> >  * Duo Zhang  
> >  * Flavio Paiva Junqueira 
> >  * Gregory Nutt   
> >  * Gustavo Henrique Nihei 
> >  * Junping Du 
> >  * Justin Mclean  
> >  * Lup Yuen Lee   
> >  * Masayuki Ishikawa  
> >  * Mohammad Asif Siddiqui 
> >  * Nathan Hartman 
> >  * Sara Monteiro  
> >  * Xiang Xiao 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
> > be appointed to the office of Vice President, Apache NuttX, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache NuttX Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator NuttX
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > NuttX podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > ]]]
> >
> > References:
> >
> > [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
> >
> > [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
> >
> > [3] https://whimsy.apache.org/roster/ppmc/nuttx
> >
> > [4] https://incubator.apache.org/guides/graduation.html
> >
> > Thanks to everyone!
> >
> > Cheers,
> > Nathan
>

Re: Post Graduation TO DO List

[Alin Jerpelea]

Congrats to us all for a great team effort!

Best regards
Alin


On Thu, Nov 17, 2022 at 5:22 PM Sebastien Lorquet 
wrote:

> Congrats!
>
> Sébastien
>
> Le 17/11/2022 à 17:20, Nathan Hartman a écrit :
> > Hi All,
> >
> > NuttX graduated from the Incubator! Kudos to the whole NuttX
> > community. Here's to a great continuation of this journey for many
> > years to come!
> >
> > Some post-graduation TODOs -- Help will be appreciated!!
> >
> > * Change NuttX and NuttX apps repo names
> >- Finalize new names
> >- Ask Infra to make the change
> >- Update all links inside our repos
> >- Announce the git incantations to update forks/clones
> >
> > * Remove DISCLAIMER from both repos
> >- See PR #7613 at NuttX repo
> >- See PR #1422 at NuttX apps repo
> >
> > * Update website:
> >- Change from Incubator to Top Level Project
> >- Update links to repos
> >
> > Cheers,
> > Nathan
>

Re: New names of repositories

[Alin Jerpelea]

hi
I think that nuttx_rtos and nuttx_apps is cleaner

Best regards
Alin



On Fri, 18 Nov 2022, 01:11 Alan C. Assis,  wrote:

> I like the second option:
>
> 2) nuttx_rtos and nuttx_apps
>
> It makes clear that it is a RTOS :-)
>
> BR,
>
> Alan
>
> On 11/17/22, Nathan Hartman  wrote:
> > Hi all,
> >
> > As mentioned in the other thread, the repos need to be renamed to
> > remove "incubating".
> >
> > In the discussion from a few months ago [1] several reasons were given
> > why not to use hyphens in the names (they confuse some tools and
> > underscores are safer).
> >
> > Two possibilities for repo names were given:
> >
> > 1) nuttx and nuttx_apps
> >
> > or
> >
> > 2) nuttx_rtos and nuttx_apps
> >
> > Which do we want?
> >
> > Cheers,
> > Nathan
> >
> > [1] https://lists.apache.org/thread/8fn2m2v8qd3sl9r8jg4bs2f9xq7mwg85
> >
>

Re: New names of repositories

[Alin Jerpelea]

how about
nuttx-core
nuttx-apps

then we locally clone to
nurtx_core
nuttx_apps

Best regards
Alim

On Sat, 19 Nov 2022, 16:50 Jukka Laitinen,  wrote:

> +1 for
>
> nuttx
> nuttx-apps
>
> Petro Karashchenko kirjoitti lauantai 19. marraskuuta 2022:
> > Hi,
> >
> > My two cents are that I think we should not rock the boat and just remove
> > "incubator-" prefix from current repos that results in:
> >
> > nuttx
> > nuttx-apps
> >
> > Best regards,
> > Petro
> >
> > сб, 19 лист. 2022 р. о 17:03 Tomek CEDRO  пише:
> >
> > > On Sat, Nov 19, 2022 at 3:53 PM Thiago Costa de Paiva wrote:
> > > > From these, the valid argument is that it would be non-standard (not
> a
> > > top level name) related to Appache rules, which I think is indeed not
> > > acceptable. It would not imply any source code organization change nor
> > > submodules:
> > > >
> > > > git clone /nuttx/core nuttx
> > > > git clone /nuttx/apps apps
> > >
> > > The use of submodules was also considered before (I also proposed
> > > that) and turned out to be a bad idea :-) :-)
> > >
> > >
> > > > Anyway, from all the discussion, since hyphens should not be used
> > > according to what Greg said previously, I think we have only two
> options:
> > > >
> > > > nuttx
> > > > nuttx_apps
> > >
> > >
> > > Then you are pro option 1 :-)
> > >
> > >
> > > On Thu, Nov 17, 2022 at 10:47 PM Nathan Hartman
> > >  wrote:
> > > > (..)
> > > > In the discussion from a few months ago [1] several reasons were
> given
> > > > why not to use hyphens in the names (they confuse some tools and
> > > > underscores are safer).
> > > >
> > > > Two possibilities for repo names were given:
> > > > 1) nuttx and nuttx_apps
> > > > or
> > > > 2) nuttx_rtos and nuttx_apps
> > >
> > > Based on my experience I am pro 2 choice as it clearly distinguishes
> > > rtos part from the apps part, is a self explanatory at first sight,
> > > and is more compatible with the potential use cases.. also as Gregory
> > > explained this nuttx_rtos part is really the whole RTOS part :-)
> > >
> > > Best regards :-)
> > > Tomek
> > >
> > > --
> > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> > >
> >

Re: New names of repositories

[Alin Jerpelea]

+1 let is as it is :)

On Sun, 20 Nov 2022, 20:23 Tomek CEDRO,  wrote:

> On Sun, Nov 20, 2022 at 8:20 PM Gregory Nutt wrote:
> >
> > On 11/20/2022 1:18 PM, Tim Hardisty wrote:
> > > Might I humbly suggest that "if it isn't broken, don't fix it"?
> > >
> > > Just stick with the names already in use (minus the incubator, as will
> happen anyway). Just tried searching the Apache website for "RTOS" and
> NuttX is top of the list; searching the Apache GitHub repositories
> similarly and NuttX is the only repo that comes up.
> > >
> > > If it does go to a vote, you can guess what mine will be for :)
> >
> > ...
> >
> > After flip-flopping for a couple of days, I have come to the same
> > conclusion as well.
>
> +1 :-) :-) :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: PinePhone added to NuttX Mainline

[Alin Jerpelea]

This is a wonderfull news!

Thanks for contributing this device

Best regards
Alin


On Sat, 26 Nov 2022, 01:07 Tomek CEDRO,  wrote:

> On Sat, Nov 26, 2022 at 1:05 AM Lee, Lup Yuen wrote:
> > Pine64 PinePhone is now supported by NuttX Mainline! If you have a
> > PinePhone (and PinePhone Serial Debug Cable), you're welcome to try NuttX
> > on PinePhone...
>
> wow! congratulations! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: Article: Preparing a Pull Request for NuttX

[Alin Jerpelea]

Nice article detailing the contribution journey

Best regards
Alin


On Mon, 28 Nov 2022, 18:58 Xiang Xiao,  wrote:

> Nice, it's very useful for new contributors.
>
> On Mon, Nov 28, 2022 at 4:07 PM Lee, Lup Yuen  wrote:
>
> > This article explains how I prepared my Pull Requests for NuttX. I hope
> > this will be helpful for folks contributing to NuttX for the very first
> > time :-)
> >
> > https://lupyuen.github.io/articles/pr
> >
> > Lup
> >
>

Re: Code donation

[Alin Jerpelea]

Hi,

thanks for the offeer

I can help with the task of review and  integrating the code in NuttX if
you push it to github

Best regards
Alin

On Mon, 5 Dec 2022, 05:44 Alan C. Assis,  wrote:

> Hi Fotis,
>
> I think all the software you listed are interesting and are useful to
> the NuttX community.
>
> As suggestion I think you could put it available on github and help
> people to help clean it up and then submit a PR to NuttX.
>
> BR,
>
> Alan
>
> On 12/4/22, Fotis Panagiotopoulos  wrote:
> > Hello everyone!
> >
> > Christmas arrived a bit earlier for NuttX as I would like to donate some
> of
> > my personal code to the community!
> >
> > A bit of context.
> > Over the years that I am working on embedded systems, I have developed
> lots
> > of software that I use in my projects.
> > Some of it is quite general-purpose, or useful for other applications,
> and
> > I have found my self reusing it
> > quite often. In fact, there are some things that I use in practically all
> > firmwares that I have developed over
> > the last years.
> >
> > I always wanted to open-source this software so other people can benefit
> > from it.
> > But I never managed to do so. Open-sourcing needs some effort, the
> software
> > needs maintenance, documentation
> > and support, and most importantly in most cases a "porting layer" needs
> to
> > be developed.
> > Last but not least, every project needs a bit of "marketing" and
> > "advertising" so others can learn about
> > your work and use it.
> >
> > For the last couple of years I have been using NuttX a lot, and I have
> > ported most of the aforementioned software
> > to NuttX. I believe that NuttX and its community are perfect for me to
> > publish my code, instead of creating
> > a ton of small repos, of questionable usefulness and increasing my
> workload
> > considerably.
> >
> > It is very important that I can get immediate feedback from the
> community,
> > learn what people are actually
> > interested in (instead of investing on software that no one needs), and
> > provide actual and *working*
> > samples of the code (as NuttX already supports a ton of different boards
> > and arches).
> >
> > Using POSIX as the porting layer is also awesome.
> >
> > That being said, my free time is still exceptionally limited and I cannot
> > do this myself.
> > I still need the help of the community, and most importantly I need to
> see
> > interest in a piece of
> > software before putting any work on it.
> >
> > So, what I offer:
> > * I offer various codes, fully featured, production ready and tested.
> > * All code will be offered for free (of course) and under Apache
> licensing.
> > * I will provide support to those working on these codes, to my best
> > ability.
> > * I will contribute to testing everything integrated to NuttX, as
> hardware
> > availability allows me.
> > * I will do some licensing check, to ensure code is 100% original and
> mine,
> > or state the licenses of the projects I borrowed code from.
> >
> > What I ask for:
> > I need people that are interested in each of these codes to integrate
> them
> > into NuttX apps.
> > You just have to pick what it is interesting to you, contact me to
> provide
> > you with the code,
> > and integrate it to NuttX. You will need to:
> > * Add the code into the NuttX apps repo, and ensure Kconfig and the build
> > system use the code properly (should be trivial).
> > * Adapt the file format and the coding style to the NuttX one (this may
> > need some work, but it can also be automated).
> > * Provide an example app, something that someone can run to use or demo
> the
> > new code.
> > * Test and verify the example app on actual hardware (I may be able to
> > cross-check it on my hardware too).
> >
> > The code that I offer (for the moment):
> >
> >
> > *** Lua v5.2.4 ***
> > I know that there is already a Lua app for NuttX.
> > But for anyone using it, it may be beneficial to use my work.
> >
> > First and foremost, I have ported the eLua LTR patch to Lua 5.2. This
> patch
> > dramatically reduces the memory usage of Lua.
> > In fact, I found out that it is crucial to have this patch enabled for
> any
> > actual real-life usage of Lua on any "normal" MCU.
> >
> > I have created a Kconfig for all Lua configurations, so it can integrate
> > with NuttX better.
> >
> > I have also made some other minor changes to the code that might be
> > interesting for you.
> > For example there is a simplistic sandboxing option.
> >
> >
> > *** MQTT Broker ***
> > Yes, a full-blown, spec-compliant MQTT Broker!
> > To my knowledge there is no other open-source and portable MQTT broker
> for
> > embedded systems.
> >
> > It follows the MQTT v3.1.1 specification as closely as possible. I think
> > there is only one violation, needed due to its embedded nature,
> > but in all practical cases you may consider it fully compliant.
> >
> > It has been tested with dozens of devices, and it performs greatly.
> > There are a couple of things that 

DISCUSS: SBOM auto generation

[Alin Jerpelea]

 Hi all,

with the increasing NuttX visibility I propose that we follow the security
and compliance trends and implement SBOM generation at build time (I can
submit the initial work)

More details:
https://www.cisa.gov/sbom

This feature should make NuttX attractive among companies and provide SW
traceability for their products.

Should we add this feature? What do you think ?

Best regards
Alin

DISCUSS: migrate licenses to SPDX

[Alin Jerpelea]

 Hi,

It looks like the SPDX standard is used by many businesses and it may have
a major deciding factor when an RTOS is picked for a product

More info regarding SPDX
https://spdx.dev/

Do you think that we should follow the trend and migrate our licenses to
the SPDX format?

Best regards
Alin

[VOTE] Apache NuttX 12.0.0 RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX 12.0.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.0.0-RC0
  Hash for the release nuttx tag: 874031bbf644c24e44c5b6af990a0c0c45d86ed3
  Hash for the release nuttx-apps tag: 5592e38253bc74c65f4d105f837d8bc048ac1859

[1] https://dist.apache.org/repos/dist/dev/nuttx/12.0.0-RC0/
[2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.0.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

Re: ROS and microROS finally working!

[Alin Jerpelea]

This is a nice Christmas news!

Thanks
Alin

On Wed, 28 Dec 2022, 13:26 Roberto Bucher,  wrote:

> Hi all
>
> I finally reached to have a system with ROS2 and microROS on Nuttx which
> seems to work correctly!
>
> The main problems were:
>
>   * Service are not working under galactic, but this seems to be a
> general problem because the freertos provided code does't work to!
> NuttX and Freertos are both working under Humble
>   * Nobody seems to handle PR for microROS. I sent 2 PR for the rcutils
> github but we no reaction! This is quite frustrating.
>
> I have a node integrated in pysimCoder that allows to exchange data
> between the NuttX embedded system and the microROS agent in a PC. It is
> possible to subscribe and publish up to 4 float64 data between the nodes
> in ROS2 and the node in microROS. Code i s available (not published yet).
>
> I'd like to have contacts with people using ROS2 and microROS with NuttX
> (there are some presentations at the Workshop!) to exchange info and
> experience.
>
> Best regards
>
> Roberto
>

[VOTE] Apache NuttX 12.0.0 RC1 release

[Alin Jerpelea]

Hello all,
Apache NuttX 12.0.0 RC1 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,


SCM Information:
  Release tag: nuttx-12.0.0-RC1
  Hash for the release nuttx tag: ccf0b5af0d6ba555f549d8d00531fa4a3a432a1b
  Hash for the release nuttx-apps tag: 5592e38253bc74c65f4d105f837d8bc048ac1859

[1] https://dist.apache.org/repos/dist/dev/nuttx/12.0.0-RC1/
[2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.0.0-RC1/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

[RESULT] Release Apache NuttX (Incubating) 12.0.0-RC1

[Alin Jerpelea]

Hi,

The vote closes now as over 72hr have passed. The vote PASSES with 4
4 (+1 binding) vote from the PMC,
0 (+0 non-binding) votes from the developer community,
No further +1, 0 or -1 votes.

The vote thread:
[1] https://lists.apache.org/thread/0gk0svgw9o8s9zk55mwbomwsvm55ncqb
The release is accepted and will be published.

Thanks,
Alin Jerpelea

[ANNOUNCE] Apache NuttX 12.0.0 released

[Alin Jerpelea]

The Apache NuttX project team is proud to announce
Apache NuttX 12.0.0 has been released.

The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/12.0.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: Article: NuttX for PinePhone: Boot to LVGL

[Alin Jerpelea]

kudos!

On Sun, 22 Jan 2023, 17:58 Tomek CEDRO,  wrote:

> CONGRATZ!! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: Video: NuttX for PinePhone

[Alin Jerpelea]

very nice!


On Wed, 8 Feb 2023, 01:10 Lee, Lup Yuen,  wrote:

> If we're curious how we download and boot NuttX on PinePhone, this video
> explains the steps...
>
> Watch on YouTube: https://youtu.be/kGI_0yK1vws
>
> Download the video (1.4 GB):
> https://github.com/lupyuen2/wip-pinephone-nuttx/releases/tag/nuttx-12.0.3
>
> (Sorry some bits look murky, this is my first time shooting in 4K)
>
> Lup
>

Re: NuttX domains available

[Alin Jerpelea]

Thanks Greg!
Let's see what the foundation says

//Alin

On Sat, 25 Feb 2023, 17:02 Alan C. Assis,  wrote:

> On 2/25/23, Tomek CEDRO  wrote:
> > On Sat, Feb 25, 2023 at 4:16 PM Gregory Nutt wrote:
> >> > Why not redirect them to https://nuttx.apache.org and crowdfund the
> >> > bills ? :-)
> >> Anyone who wants to pay for the domains is welcome to do that.  I am
> >> finished paying.
> >
> > Sure thing Greg! Maybe Apache could support crowdfunding and hosting?
> > If not I can handle them :-)
> >
>
> I agree Apache should take care of it!
>
> If they cannot help I think we can divide the expenses.
>
> BR,
>
> Alan
>

Re: [Breaking change] Echo character by serial driver

[Alin Jerpelea]

Hi,

In my opinion we should keep the memory usage as low as possible
+1 for menu config

Best Regards
Alin

On Sat, 11 Mar 2023, 05:13 Xiang Xiao,  wrote:

> On Sat, Mar 11, 2023 at 9:51 AM Gregory Nutt  wrote:
>
> >
> > On 3/10/2023 7:44 PM, Huang Qi wrote:
> > > >>  The ECHO behavior can be disabled ONLY if TERMIOS are enabled.
> > > >>  TERIMIOS is now required by POSIX and, further, if TERMIOS is not
> > > >>  system, many features are now broken.  Like hiding the password
> when
> > > >>  logging into NSH.
> > > > Yes maybe we should select TERMIOS if some features really need it ?
> > > Most apps don't need it, only
> > > > termcurse/nsh login rely on it now in my known.
> > >
> > > > The those Kconfig files should select TERMIOS_SERIAL, right?
> > >
> > > Yes, this is a chioce, or we can make TERMIOS enabled forcely, but
> > > will cause a extra 1KB overhead for all target.
> > >
> > That 1Kb number seems large to me.  Most of that is in the lower-half,
> > UART driver, right?  If so then the size would vary dramatically from
> > chip-to-chip.
> >
> >
> Terminal setting include two part:
>
>1. Hardware related setting(e.g. baud rate, parity check etc)
>2. Software related setting(e.g. echo, \r\n<->\n etc)
>
> The major code size increase comes from the first item, but it's
> unfortunate that TERMIOS_SERIAL controls both settings.
> So, here is my suggestion:
>
>1. TERMIOS_SERIAL only control the hardware related setting
>2. The software setting is always enabled
>3. isconsole decide the initial software setting
>   - isconsole equals false, disable all special process
>   - isconsole equals true, enable \r\n<->\n, echo and crtl+c handling
>4. terminal aware function or application change the terminal to raw
>mode and restore to the original setting before exit
>5. other normal application could assume that the terminal do all
>special process
>
> This could achieve POSIX compliance with the minimal cost.
>
>
> >
> > As a percentage growth, I suppose even 1Kb is not so large.  Probably
> > less then 2%
> >
>

Re: Embedded World 2023

[Alin Jerpelea]

hi
I will be there and I hope to meet some of our awesome community members

Best regards
Alin

On Sun, 12 Mar 2023, 17:06 Nathan Hartman,  wrote:

> On Sun, Mar 12, 2023 at 7:48 AM Fotis Panagiotopoulos  >
> wrote:
>
> > Hello,
> >
> > Is anyone planning a visit to Embedded World?
> >
> > I am flying tonight to Nuremberg.
> > It would be nice if we can arrange a meet-up!
> >
> > Fotis.
> >
>
> I can't attend unfortunately but just wanted to say that if you could do a
> little bit of evangelizing for NuttX and tell people about this project,
> that would be awesome!
>
> Safe travels!
>
> Cheers,
> Nathan
>

Re: [Breaking change] NRF52 NVMC and FLASH support should depends on BSD components

[Alin Jerpelea]

I don't think that we should add #ifdef to the code.
We can use the same Kconfig exclusion as on the other components

Best regards
Alin

On Sat, 18 Mar 2023, 09:00 raiden00pl,  wrote:

> Wrapping the entire file with '#ifdef' makes debugging complex preprocessor
> logic a nightmare, so I'm not a fan of this idea.
> Looking for the missing `#endif` in such a file can be really frustrating.
>
> pt., 17 mar 2023 o 16:42 Nathan Hartman 
> napisał(a):
>
> > On Wed, Mar 15, 2023 at 6:16 AM raiden00pl  wrote:
> > >
> > > NVMC support for NRF52 chips was ported from Nordic SDK which was
> > released
> > > on the BSD license (old times), so these features should depend on
> > > CONFIG_ALLOW_BSD_COMPONENTS=y. Users must manually enable support for
> the
> > > BSD components to continue using the mentioned features.
> > >
> > > Related PR: https://github.com/apache/nuttx/pull/8827
> >
> >
> > Thanks for posting about it to the list. I just added my review there,
> > but it got me thinking:
> >
> > We have many files listed in LICENSE which are non-Apache-2.0-License
> > and I haven't had a chance to check but I have a feeling that there
> > could be more files that should be protected by ALLOW_BSD_COMPONENTS /
> > ALLOW_MIT_COMPONENTS / ALLOW_GPL_COMPONENTS / ALLOW_*_COMPONENTS that
> > are not currently protected.
> >
> > For each file that has a non-Apache-2.0-License at the top, should we
> > wrap the entire file contents with:
> >
> > #ifdef ALLOW_*_COMPONENTS
> > .
> > .
> > .
> > #endif /* ALLOW_*_COMPONENTS */
> >
> > (for the appropriate value of * of course)?
> >
> > Yes, doing that will cause compiler errors when a build tries to use
> > those files and doesn't have the required ALLOW_*_COMPONENTS enabled,
> > but that will help us find all those cases relatively quickly and fix
> > them by adding "depends on ALLOW_*_COMPONENTS" in Kconfig.
> >
> > It will ensure that when someone doesn't choose ALLOW_BSD_COMPONENTS /
> > ALLOW_MIT_COMPONENTS / ALLOW_GPL_COMPONENTS then their build will
> > actually be licensed as advertised.
> >
> > If we want to do it then obviously it should be separate PRs, maybe
> > one for each component we find...
> >
> > Thoughts?
> >
> > Nathan
> >
>

[VOTE] Apache NuttX 12.1.0 RC0 release

[Alin Jerpelea]

Hello all,
Apache NuttX 12.1.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.1.0-RC0
  Hash for the release nuttx tag: d40f4032fc5491d2aeb9fde37042a5be9eabeb15
  Hash for the release nuttx-apps tag: 125cf7abe2d7f345c3bc58c0bdea2360fdefa170

[1] https://dist.apache.org/repos/dist/dev/nuttx/12.1.0-RC0/
[2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.1.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

Re: V NuttX International Workshop

[Alin Jerpelea]

1 laptop streaming and and at least 1 online moderator would bridge the gap
between phosical and online.
I offer muself to be one of the moderators

Best regards
Alin

On Sun, 16 Apr 2023, 16:59 Tomek CEDRO,  wrote:

> On Sun, Apr 16, 2023 at 4:35 PM Alan C.  wrote:
> >
> > On 4/16/23, Nathan Hartman  wrote:
> > > Perhaps the simplest low-tech way is to video tape the presentations
> and
> > > post the videos online afterwards.
> > >
> > > In fact, not only will this make it possible to see the event for
> people
> > > who can't attend, but it will also become possible to refer back to the
> > > presentations for people who do attend, and can be added to our online
> > > video repertoire for people who discover NuttX in the future.
> > >
> > > So, if it is possible , I hope the presentations can be video taped
> and put
> > > online.
> > >
> >
> > Yes, his is an option, but if we can do live stream to let people to
> > participate as in previous Online Workshop will be awesome! :-)
> >
> > Tiago told me that Unicamp has some equipment to do that, let see if
> > we could use it.
>
> I guess ESP32CAM running NuttX will do the job  + external obs/vlc server
> :-)
>
> Alternatively Google Meet or Zoom should be fine :-)
>
> Thanks Alan! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

[RESULT] Release Apache NuttX 12.1.0 [RC0]

[Alin Jerpelea]

Hi,

The vote closes now as over 72hr have passed. The vote PASSES with 4
(+4 binding) votes from the PPMC,
1 (+0 non-binding) votes from the developer community,
No further +1, 0 or -1 votes.

The vote thread:
[1] https://lists.apache.org/list.html?dev@nuttx.apache.org

Thanks,
Alin Jerpelea

[ANNOUNCE] Apache NuttX 12.1.0 released

[Alin Jerpelea]

The Apache NuttX project team is proud to announce Apache NuttX 12.1.0 released.

The release artifacts and Release Notes can be found
at:https://nuttx.apache.org/download/https://nuttx.apache.org/releases/12.1.0/

Thanks,
Alin Jerpelea
on behalf of Apache NuttX PPMC

Re: 12.1.0 vs 12.1

[Alin Jerpelea]

thanks for spotting the error
Best Regards
Alin

On Thu, 11 May 2023, 03:52 Tomek CEDRO,  wrote:

> On Thu, May 11, 2023 at 3:42 AM Brennan Ashton wrote:
> > On Wed, May 10, 2023, 6:34 PM Tomek CEDRO wrote:
> > > Silly question.. why some places use release name 12.1.0 (i.e. running
> > > firmware) and some other places use 12.1?
> > > Shouldn't we stick to one coherent versioning convention? 12.1.0?
> >
> > Since becoming an Apache project all releases have used the
> > major.minor.patch format. Some previous release use major.minor
> >
> > Can you link to a place where we are only using 12.1 without the patch.
>
> Thanks Brennan :-) I saw 12.1 on that Hackster stuff.. probably a
> typo.. will update to 12.1.0 :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: NuttX Internation Workshop Call for Paper is open!

[Alin Jerpelea]

yes we do and we would be happy to see many speakers around the globe for
the NuttX Iinternational Workshop

Best regards
Alin

On Sun, 11 Jun 2023, 17:34 Mark Stevens,  wrote:

> Are you allowing remote presentations ?
>
> Regards,
> Mark
> _
> Blog: blog.thepcsite.co.uk
> Twitter: @nevynuk
>
>
>
>
>
> > On 11 Jun 2023, at 14:52, Alan C. Assis  wrote:
> >
> > Please submit your proposal:
> >
> > https://events.nuttx.apache.org
>
>

Re: NuttX Internation Workshop Call for Paper is open!

[Alin Jerpelea]

Hi Masayuki-san,

the corect date is August. I will correct the site. Thanks for for finding
the mistake

Best regards
Alin

On Tue, 13 Jun 2023, 02:27 Masayuki Ishikawa, 
wrote:

> Hi Alan,
>
> According to the website, I can find the following information.
>
> ==
> Active participation proposals should be submitted until 18th July 2023 via
> the links available at www.events.nuttx.apache.org.
> Successful candidates will be informed of the success of their application
> by 25th July 2023.
>
>
> *IMPORTANT DATES*Participation proposals deadline: 18th August 2023
> Participation proposals acceptance notification: 25th August 2023
> ==
> Which dates are correct? (July or August)
>
> On Mon, Jun 12, 2023 at 3:16 AM Alan C. Assis  wrote:
>
> > Yes, we will have mixed presentations (real/virtual).
> >
> > On 6/11/23, Mark Stevens  wrote:
> > > Are you allowing remote presentations ?
> > >
> > > Regards,
> > > Mark
> > > _
> > > Blog: blog.thepcsite.co.uk
> > > Twitter: @nevynuk
> > >
> > >
> > >
> > >
> > >
> > >> On 11 Jun 2023, at 14:52, Alan C. Assis  wrote:
> > >>
> > >> Please submit your proposal:
> > >>
> > >> https://events.nuttx.apache.org
> > >
> > >
> >
>

[VOTE] Apache NuttX 12.2.0 RC0 release

[Alin Jerpelea]

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

Re: [VOTE] Apache NuttX 12.2.0 RC0 release

[Alin Jerpelea]

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/bi

Re: release branches strings and notes :-)

[Alin Jerpelea]

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: release branches strings and notes :-)

[Alin Jerpelea]

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: [VOTE] Apache NuttX 12.2.0 RC0 release

[Alin Jerpelea]

Thanks for all the info
Best Regards
Alin

On Sat, 1 Jul 2023, 21:28 Alan C. Assis,  wrote:

> Yes, that is perfect! Thank you!
>
> On 7/1/23, Roberto Bucher  wrote:
> > Hi Alan
> >
> > I hope that these info can are complete:
> >
> > Configuration:
> >  nucleo-144:f746-pysim
> >
> > Configuration for pysimCoder including network (DHCP) support
> >
> > ls -l:
> > -rwxr-xr-x  1 bucher bucher 1744196 Jun 22 11:06 nuttx
> > -rwxr-xr-x  1 bucher bucher  134400 Jun 22 11:06 nuttx.bin
> > -rw-r--r--1 bucher bucher 2406500 Jun 30 16:11
> > nuttx-export-12.2.0.tar.gz
> >
> > NuttX shell:
> >
> > nsh> ?
> > help usage:  help [-v] []
> >
> >  . basename  ddfalse lsnslookup
> > route truncate
> >  [ break delroute  free  lsmod printf set
> > uname
> >  ? cat   dfhelp  mkdir ps sleep umount
> >  addroute  cddmesg hexdump   mkfifopwd source
> unset
> >  alias cpecho  ifconfig  mkrd  rm test uptime
> >  unalias   cmp   exec  insmodmount rmdir time
> > usleep
> >  arp   dirname   exit  kill  mvrmmod true  xd
> >
> > Builtin Apps:
> >  nsh  ping renewsh   telnetd  main
> > nsh> ls dev
> > /dev:
> >   adc0
> >   can0
> >   console
> >   gpio0
> >   gpio1
> >   gpio10
> >   gpio11
> >   gpio12
> >   gpio2
> >   gpio3
> >   gpio4
> >   gpio5
> >   gpio6
> >   gpio7
> >   gpio8
> >   gpio9
> >   null
> >   ptmx
> >   pwm0
> >   qe2
> >   qe3
> >   telnet
> >   ttyS0
> >
> > Bye
> >
> > Roberto
> >
> > On 7/1/23 14:16, Alan C. Assis wrote:
> >> Hi Roberto,
> >>
> >> Could you please supply more information? toolchain version used, size
> >> of final binary, etc
> >>
> >> This way to can have a historic of all versions.
> >>
> >> BR,
> >>
> >> Alan
> >>
> >> On 7/1/23, Roberto Bucher  wrote:
> >>> +1
> >>>
> >>> Tested on nucleo-144 (STM32F746ZG) + pysimCoder
> >>>
> >>> Roberto
> >>>
> >>> On 6/30/23 10:47, 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
> >>>>
> >>>
> >
> >
>