On Fri, Jun 26, 2020 at 9:35 AM Jerpelea, Alin
wrote:
> Hi Justin,
>
> I can confirm that the latest branch looks good
> We should create RC1 wih the fixes included to start the testing and
> voting for RC1
What about the bug report about mm_realloc() reported by a user on 24 Jun:
NuttX 9.1.0 (incubating) RC0 release
HI,
> I confirmed that the latest releases/9.1 branch fixes the problems.
A vote need to be on a static code base / a release artefact not what is in a
branch. It can’t change as the hashes and signatures would be different for
starters.
Thanks,
Justin
On Fri, Jun 26, 2020, 5:40 AM Justin Mclean
wrote:
> HI,
>
> > I confirmed that the latest releases/9.1 branch fixes the problems.
>
> A vote need to be on a static code base / a release artefact not what is
> in a branch. It can’t change as the hashes and signatures would be
> different for
HI,
> I confirmed that the latest releases/9.1 branch fixes the problems.
A vote need to be on a static code base / a release artefact not what is in a
branch. It can’t change as the hashes and signatures would be different for
starters.
Thanks,
Justin
+1
I confirmed that the latest releases/9.1 branch fixes the problems.
Masayuki
From: Brennan Ashton
Sent: Friday, June 26, 2020 14:17
To: dev@nuttx.apache.org
Cc: Ishikawa, Masayuki (SHES)
Subject: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
+1
Op wo 24 jun. 2020 02:40 schreef Brennan Ashton :
> On Tue, Jun 23, 2020 at 5:36 PM Brennan Ashton
> wrote:
> >
> > On Tue, Jun 23, 2020 at 5:35 PM Brennan Ashton
> > wrote:
> > >
> > > On Tue, Jun 23, 2020 at 5:31 PM Justin Mclean <
> jus...@classsoftware.com> wrote:
> > > >
> > > > Hi,
>
) RC0 release
Here is the fix we sent two days ago:
https://github.com/apache/incubator-nuttx-apps/pull/303
From: Ishikawa, Masayuki (SHES)
Sent: Friday, June 26, 2020 10:13 AM
To: dev@nuttx.apache.org; Xiang Xiao
Subject: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
Hi, Xiang
On Thu, Jun 25, 2020 at 10:10 PM Xiang Xiao wrote:
>
> Here is the fix we sent two days ago:
>
> https://github.com/apache/incubator-nuttx-apps/pull/303
>
Backports PRs are available for both this and the RISCV elf bug
https://github.com/apache/incubator-nuttx/pull/1306
Here is the fix we sent two days ago:
https://github.com/apache/incubator-nuttx-apps/pull/303
From: Ishikawa, Masayuki (SHES)
Sent: Friday, June 26, 2020 10:13 AM
To: dev@nuttx.apache.org; Xiang Xiao
Subject: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
Hi, Xiang and all
this issue?
Perhaps, something is wrong with the build system.
Thanks,
Masayuki
From: Brennan Ashton
Sent: Tuesday, June 23, 2020 15:36
To: dev@nuttx.apache.org
Subject: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
Hello all,
Apache NuttX (Incubating) 9.1.0 has
On Wed, Jun 24, 2020, 10:56 AM Gregory Nutt wrote
>
> My concern is that if we sweep things under the carpet now and continue
> with the 9.1 eyes shut as if there is nothing wrong, we will continue to
> degrade the OS footprint over time. It requires aggressive action to
> control the binary
the "small" of NuttX. So some of these "clean up" PR's should have
a little more eyes on them.
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Wednesday, June 24, 2020 6:26 AM
To: dev@nuttx.apache.org
Subject: Re: [VOTE] Apache NuttX 9.1.0 (inc
On 6/24/2020 9:20 AM, Alan Carvalho de Assis wrote:
Hi Greg,
On 6/24/20, Gregory Nutt wrote:
Changing the default is not the problem. The problem is when the
default configuration value is changed, the all configurations effected
by that change in the default setting should be updated so
Yes, it should be nice to have bloaty integrated on CI system to ring
an alarm when something like this happen.
If it works as advertised, then this would be a good idea. Some gradual
code growth is natural natural due to the nature of the NuttX roadmap --
to be a complete, small POSIX OS
Hi Greg,
On 6/24/20, Gregory Nutt wrote:
>
> Changing the default is not the problem. The problem is when the
> default configuration value is changed, the all configurations effected
> by that change in the default setting should be updated so that they are
> not effected. That is, so the net
> From: Brennan Ashton [mailto:bash...@brennanashton.com]
> Sent: Tuesday, June 23, 2020 10:53 PM
> To: dev@nuttx.apache.org
> Subject: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
>
> Greg and Alan,
> Started looking and there are some changes in the diff in the
&
Started looking and there are some changes in the diff in the
generated config.h as can be seen here
One change is the date command is no longer disabled by default. This
accounts for 2304 bytes, leaving only 800 byte change.
I'm not sure if changing the default was expected, but I dont think
Ashton [mailto:bash...@brennanashton.com]
Sent: Tuesday, June 23, 2020 10:53 PM
To: dev@nuttx.apache.org
Subject: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
Greg and Alan,
Started looking and there are some changes in the diff in the
generated config.h as can be seen here
One change
+1,
I checked
- Signature and hash OK
- LICENSE, DISCLAIMER and NOTICE exist
- Build from source.Spresense board
Från: Brennan Ashton
Skickat: den 24 juni 2020 07:52
Till: dev@nuttx.apache.org
Ämne: Re: [VOTE] Apache NuttX 9.1.0 (incubating) RC0 release
Greg
Greg and Alan,
Started looking and there are some changes in the diff in the
generated config.h as can be seen here
One change is the date command is no longer disabled by default. This
accounts for 2304 bytes, leaving only 800 byte change.
I'm not sure if changing the default was expected, but I
those are the bin and config diffs between 9.0 and 9.1 for Spresense board
(nsh defconfig)
file size
2232796 Jun 24 07:34 nuttx-9.0
2274908 Jun 24 07:31 nuttx-9.1
--- conf-9.02020-06-24 07:34:00.244923392 +0200
+++ conf-9.12020-06-24 07:30:35.748476384 +0200
@@ -129,10 +129,8 @@
#
+1,
I checked
- Signature and hash OK
- LICENSE, DISCLAIMER and NOTICE exist
- Build from source.Spresense board
On Wed, Jun 24, 2020 at 3:17 AM Gregory Nutt wrote:
> On 6/23/2020 6:59 PM, Gregory Nutt wrote:
> >
> >> I compared it to release 9.0 and noticed it increased about 3 KiB of
> >>
On 6/23/2020 6:59 PM, Gregory Nutt wrote:
I compared it to release 9.0 and noticed it increased about 3 KiB of
Flash usage, but I didn't check further to see what happened.
NuttX 9.0
$ arm-none-eabi-size nuttx
text data bss dec hex filename
68624
I compared it to release 9.0 and noticed it increased about 3 KiB of
Flash usage, but I didn't check further to see what happened.
NuttX 9.0
$ arm-none-eabi-size nuttx
text data bss dec hex filename
686241042496 71224 11638 nuttx
NuttShell
Hi,
> This key is not expired and has been signed by my apache.org email address as
> well
Thanks for that I must of had an old cached key.
Setting your expiry dates to the near future may not be a good idea as I seem
to recall releases with expired key were removed from the mirrors at one
On Tue, Jun 23, 2020 at 5:36 PM Brennan Ashton
wrote:
>
> On Tue, Jun 23, 2020 at 5:35 PM Brennan Ashton
> wrote:
> >
> > On Tue, Jun 23, 2020 at 5:31 PM Justin Mclean
> > wrote:
> > >
> > > Hi,
> > >
> > > I’ve not done a full check (which I will do) but I would be -1 on this
> > > release
On Tue, Jun 23, 2020 at 5:35 PM Brennan Ashton
wrote:
>
> On Tue, Jun 23, 2020 at 5:31 PM Justin Mclean
> wrote:
> >
> > Hi,
> >
> > I’ve not done a full check (which I will do) but I would be -1 on this
> > release as it looks like it’s been signed with an expired key:
> >
> > gpg: Good
On Tue, Jun 23, 2020 at 5:31 PM Justin Mclean wrote:
>
> Hi,
>
> I’ve not done a full check (which I will do) but I would be -1 on this
> release as it looks like it’s been signed with an expired key:
>
> gpg: Good signature from "Brennan Ashton "
> [expired]
> gpg: Note: This key has expired!
Hi,
I’ve not done a full check (which I will do) but I would be -1 on this release
as it looks like it’s been signed with an expired key:
gpg: Good signature from "Brennan Ashton " [expired]
gpg: Note: This key has expired!
It's also a good idea to sign with an “@apache.org” email address.
Hi,
> Does this mean that if you do not validate anything, you lose your right as a
> PPMC member to vote?
No, merit once gained isn’t lost, but it could be a little embarrassing if a
critical issue is found after the release has been made. In that case another
release is needed to correct
Hi Brennan,
I did a basic test on STM32F4Discovery board compiling the "nsh" and
everything worked fine (see below).
My VOTE: +1
I compared it to release 9.0 and noticed it increased about 3 KiB of
Flash usage, but I didn't check further to see what happened.
NuttX 9.0
$ arm-none-eabi-size
>
> In the past, I thought we decided that any [VOTE] phase must be preceded
> by a [DISCUSS] phase?
>
This email is basically boiler plate that is following the process that
Apache defines for the podling release process and is the same as what we
did for the last release. There is no obligation
On 6/23/2020 12:36 AM, Brennan Ashton wrote:
Hello all,
Apache NuttX (Incubating) 9.1.0 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.
Because this project targets embedded
On 6/23/2020 12:36 AM, Brennan Ashton wrote:
Hello all,
Apache NuttX (Incubating) 9.1.0 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.
Because this project targets embedded
Hi,
+1, I checked:
- Incubating in name
- Signature and hash OK
- LICENSE, DISCLAIMER and NOTICE exist
- Build from source.
On Tue, Jun 23, 2020 at 7:37 AM Brennan Ashton
wrote:
>
> Hello all,
> Apache NuttX (Incubating) 9.1.0 has been staged under [1] and it's time to
> vote
> on accepting it
Hello all,
Apache NuttX (Incubating) 9.1.0 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.
Because this project targets embedded systems there is more complexity involved
in
36 matches
Mail list logo
