Only PMC/committer have the permission to update those repositories if I
remember correctly, so we can manage github.com/nuttx using the same Apache
process.
> -Original Message-
> From: Gregory Nutt
> Sent: Saturday, August 15, 2020 3:27 AM
> To: dev@nuttx.apache.org
> Subject: Re: cpp
Yes, I will post the patch to llvm libcxx email list.
> -Original Message-
> From: Alan Carvalho de Assis
> Sent: Saturday, August 15, 2020 3:23 AM
> To: dev@nuttx.apache.org
> Subject: Re: cpp cxx help - No thread API
>
> Guys, I think we should move your bitbucket libcxx to github.com/
I think the usual approach is to use milestones for tracking versions and
distribute issues to those and projects
to track a "big feature" which is composed of many individual tasks. The other
difference is that projects allow to create "cards" (like sticky notes) which
can be later converted (o
On 8/14/2020 3:39 PM, Abdelatif Guettouche wrote:
We've already agreed on the version numbering. It's pretty much the
same as it was + the patch number. So if there is incompatible change
to the APIs, we need to bump the major number to 10.
of course, there are degreses of incompatibility. 7
We've already agreed on the version numbering. It's pretty much the
same as it was + the patch number. So if there is incompatible change
to the APIs, we need to bump the major number to 10.
> wouldn't you like to create a milestone for next version as well?
We used Github Project last time to
You will find this page helpful:
https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
> On Aug 14, 2020, at 1:02 PM, Brennan Ashton wrote:
>
> Dave,
> Thanks for the heads up. We did not know about this (I'll subscribe
> to the build list), it looks like w
Dave,
Thanks for the heads up. We did not know about this (I'll subscribe
to the build list), it looks like we need to file a ticket for a new
folder to be created for the project (NuttX). I'll do that now and
try to migrate tonight.
Thanks
--Brennan
On Fri, Aug 14, 2020 at 12:49 PM Dave Fisher
Hi Dave,
thanks for reaching out - as Tamaya is about to retire I decided not to
do anything.
Cheers & happy weekend
Phil
Am 14.08.20 um 21:48 schrieb Dave Fisher:
> Hi -
>
> There is a critical migration for Jenkins builds that the project is missing.
>
> Several PMC members ought to be subs
On Fri, Aug 14, 2020 at 2:51 PM Gregory Nutt wrote:
>
> > Nathan started this here:
> > https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.2
> >
> > I would say let's fill that out, we can change it to 10.0 later. I
> > will kick off getting the tracking board and the PR changes going in
Hi -
There is a critical migration for Jenkins builds that the project is missing.
Several PMC members ought to be subscribed to bui...@apache.org.
Please act quickly.
Regards,
Dave
> Begin forwarded message:
>
> From: Gavin McDonald
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> Date
Guys, I think we should move your bitbucket libcxx to github.com/nuttx
to make it more official.
What do you think? Other (better) option should including official
support to NuttX on llvm libcxx.
i would NEVER recommend github.com/nuttx for any significant use. There
are many people with
Guys, I think we should move your bitbucket libcxx to github.com/nuttx
to make it more official.
What do you think? Other (better) option should including official
support to NuttX on llvm libcxx.
BR,
Alan
On 8/14/20, Xiang Xiao wrote:
> This is because Alan's porting isn't compatible with the
Nathan started this here:
https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.2
I would say let's fill that out, we can change it to 10.0 later. I
will kick off getting the tracking board and the PR changes going in
next week, that I thought worked quite well for realtime and async
coll
This is because Alan's porting isn't compatible with the NuttX's latest master.
Please try this patch which integrate the latest libc++(11.0.0-rc1) into NuttX:
https://github.com/apache/incubator-nuttx/pull/1592
Note: you don't need git clone libc++ manually, Makefile will do this
automatically.
Hi,
wouldn't you like to create a milestone for next version as well? We could then
assign issues that should be fixed/completed
and included in 10.0, leaving out those that should be left for next versions.
I'm not quite sure what the GH project offers but it seems it is not
necessarily used fo
Thanks for bringing this up Greg, I was also starting to think it was
about time to plan a release.
On Fri, Aug 14, 2020 at 10:55 AM Gregory Nutt wrote:
>
> We finally released 9.1.0 on 2020-07-22. I think the target date for
> that one was 2020-07-01, wasn't it. The next release should then be
We finally released 9.1.0 on 2020-07-22. I think the target date for
that one was 2020-07-01, wasn't it. The next release should then be
sometime next month, right? 2020-09-01? Or 2020-09-22?
I don't know what the policy of the NuttX Incubator is, but prior to
Apache, I used the major revis
17 matches
Mail list logo
