Hi, all
If we are serious about getting on a two month release cycle again, now
is the time to begin thinking about the 9.1 release. We created the 9.0
release branch sometime before the 15th of April. We signed the
release on April 23rd. So we have some time, but also we need to start
get
On Wed, Jun 3, 2020, 6:16 AM Gregory Nutt wrote:
> Hi, all
>
> If we are serious about getting on a two month release cycle again, now
> is the time to begin thinking about the 9.1 release. We created the 9.0
> release branch sometime before the 15th of April. We signed the
> release on April 2
Brennan,
What, in your opinion, needs to be done to improve the onboarding process?
And what would you like to see happen to improve the licensing issues?
Another pass through the files of another section (like we did with sched)
and updating headers? Or...?
-adam
On Wed, Jun 3, 2020 at 8:44 AM
For the licensing, we are taking baby steps by changing only the files
that we know won't cause any issue.
I think we will continue to do that until we get the necessary ICLAs
then we can do a massive substitution.
But as have been said in the very beginning, this should not stop us
from making rel
Abdelatif,
I haven't tried my instructions on macOS... when I was first starting out,
I got stuck, and switched to Linux. But I will give macOS a try again in
the next few days, and update the instructions if I succeed. Good idea.
Re: the release notes, maybe we can start using a template for PR
I only mentioned macOS because one of the mentors was using it the
last time, I guess what's important is to have instructions that start
from a fresh installation of any OS and end with a usable workstation,
I'm sure there are plenty for Linux.
> Re: the release notes, maybe we can start using a
On Wed, Jun 3, 2020 at 5:36 PM Adam Feuer wrote:
> I got stuck, and switched to Linux. But I will give macOS a try again in
> the next few days, and update the instructions if I succeed.
I built a recent master on macOS and it worked. All I had to do was:
* Install gcc-arm-none-eabi using inst
On Wed, Jun 3, 2020 at 2:12 PM Abdelatif Guettouche
wrote:
> Generating release notes is the part that has the most painful work,
> it took 4 of us last time to get it done. I still wonder if there is
> a way to automate that, maybe with good PR summaries and consistent
> labeling.
> Nathan creat
Should we continue triaging PRs during the 7th-15 period?
Then we stop and only backport what's necessary when the branch is
created (i.e. 15th)?
I also want to reiterate the backporting procedure. Xiang was
suggesting to create only one PR with all the commits cherry-picked.
GIT wise we will alw
, June 08, 2020 5:03 AM
To: dev@nuttx.apache.org
Subject: Re: Release 9.1
Should we continue triaging PRs during the 7th-15 period?
Then we stop and only backport what's necessary when the branch is
created (i.e. 15th)?
I also want to reiterate the backporting procedure. Xiang was
suggesti
m]
> Sent: Monday, June 08, 2020 5:03 AM
> To: dev@nuttx.apache.org
> Subject: Re: Release 9.1
>
> Should we continue triaging PRs during the 7th-15 period?
> Then we stop and only backport what's necessary when the branch is
> created (i.e. 15th)?
>
> I also want to reite
On Mon, Jun 8, 2020 at 6:21 AM Abdelatif Guettouche
wrote:
>
> > Would tags do the same thing?
> > How does this work over time?
> > Many PRs or keep force pushing to the PR
>
> For each release there will be only one PR that hosts all the
> backported commits.
> And yes, tags would work I guess,
> I'm also not clear are we talking about git tags here or github
> labels? We are using git tags but that is when we cut the release on
> the release branch.
I don't know why I assumed Github labels and not git tags. I was
obviously talking about Github labels. I'm not sure how David sees
the u
aster has testing, bug fix Backport PR should be merged with 0
delay.
David
-Original Message-
From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
Sent: Tuesday, June 09, 2020 5:02 AM
To: dev@nuttx.apache.org
Subject: Re: Release 9.1
> I'm also not clear are we
-Original Message-
> From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> Sent: Tuesday, June 09, 2020 5:02 AM
> To: dev@nuttx.apache.org
> Subject: Re: Release 9.1
>
> > I'm also not clear are we talking about git tags here or github
> > labels?
. If
> > it is in the Title it will help filter emails. Not sure if the labels are
> > helpful in an inbox but are on Github.
> >
> > Assuming master has testing, bug fix Backport PR should be merged with 0
> > delay.
> >
> >
> > David
> >
>
On Mon, Jun 15, 2020 at 8:58 AM Abdelatif Guettouche
wrote:
> Hi all,
>
> D-Day; I'll go ahead and create the branches.
Thank you!
I went ahead and created a blank release notes wiki for the *next*
release, 9.2, here:
https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.2
If there's anythi
Thanks Nathan,
> if there's anything else to add to the 9.1 release notes, that page
> remains here:
> https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.1
I think there is one PR in nuttx/ that's not included in the release
notes and maybe two in apps/. That should be quick.
Another thin
On Mon, Jun 15, 2020, 9:14 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Thanks Nathan,
>
> > if there's anything else to add to the 9.1 release notes, that page
> > remains here:
> > https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.1
>
> I think there is one PR in nu
19 matches
Mail list logo
