Build failed in Jenkins: NuttX-Nightly-Build #110

See Changes: -- [...truncated 4.73 MB...] sched/pthread_mutexunlock.d sched/pthread_release.d sched/pthread_setaffinity.d sched/pthread_setschedparam.d

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

+1 Ran the Validating a Staged Release procedure , all ok. Compiles and runs on SAMA5D3-Xplained board. -adam On Tue, Apr 28, 2020 at 9:22 AM Alan Carvalho de Assis wrote: > +1 > > On 4/28/20, Brennan Ashton wrote

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

+1 On 4/28/20, Brennan Ashton wrote: > Hello all, > Apache NuttX (Incubating) 9.0.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. > > This release includes fixes on

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

+1 Thanks for your hard work On Tue, Apr 28, 2020, 17:33 Gregory Nutt wrote: > +1 > > Its been a long time coming! > > On 4/28/2020 12:06 AM, Brennan Ashton wrote: > > Hello all, > > Apache NuttX (Incubating) 9.0.0 has been staged under [1] and it's time > to > > vote > > on accepting it for re

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

+1 Its been a long time coming! On 4/28/2020 12:06 AM, Brennan Ashton wrote: Hello all, Apache NuttX (Incubating) 9.0.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. This

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

Thank you, Brennan! +1 for me. I checked: - Incubating in name, - Signatures and hashes are correct, - LICENSE, DISCLAIMER and NOTICE exist, - Everything builds and works fine. On Tue, Apr 28, 2020 at 7:06 AM Brennan Ashton wrote: > > Hello all, > Apache NuttX (Incubating) 9.0.0 has been

Re: Direct commits to repository

On Tue, Apr 28, 2020 at 10:49 PM Nathan Hartman wrote: > > On Tue, Apr 28, 2020 at 10:38 AM Gregory Nutt wrote: > > > > The maintainer still can create a new branch and push to that branch > > directly, only the master branch get the strict protection. The setting > > must be done by INFRA team

Re: Direct commits to repository

> I'm guessing that for this particular instance, someone could fork the repo > and then open a PR from their SocketCAN branch to our master? But. We can open a pull request from the main repo. What Xiang is suggesting is to only protect master or any other branch pattern we want. That won't

Re: Direct commits to repository

On Tue, Apr 28, 2020 at 10:38 AM Gregory Nutt wrote: > > The maintainer still can create a new branch and push to that branch > directly, only the master branch get the strict protection. The setting > must be done by INFRA team, I can raise a JIRA ticket if the community > agree that it's the

Re: Direct commits to repository

> The maintainer still can create a new branch and push to that branch directly, only the master branch get the strict protection.  The setting must be done by INFRA team, I can raise a JIRA ticket if the community agree that it's the right direction to go. How would we perform development on

RE: Direct commits to repository

Way back when, I added a no_push to prevent any direct pushing. This may help others. git remote set-url --push origin no_push *From:* Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com] *Sent:* Monday, April 27, 2020 10:26 PM *To:* dev@nuttx.apache.org *Subject:* Re: Direct comm