n Ashton [mailto:bash...@brennanashton.com]
> Sent: Sunday, October 18, 2020 10:25 PM
> To: dev@nuttx.apache.org
> Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule
>
> On Sat, Oct 17, 2020 at 6:37 AM Abdelatif Guettouche
> wrote:
> >
> > Thanks for merging, Brennan!
> &g
Thank you Brennan for all your efforts!
David
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Sunday, October 18, 2020 10:25 PM
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule
On Sat, Oct 17, 2020 at 6:37 AM Abdelatif
Kudos Brennan!
On 10/19/20, Brennan Ashton wrote:
> On Sat, Oct 17, 2020 at 6:37 AM Abdelatif Guettouche
> wrote:
>>
>> Thanks for merging, Brennan!
>>
>> I'll work on some more today.
>> It'd be great if others can help, there are 515 PRs left :D
>> In any case, here are the links:
>> Github Pr
Thanks Brennan!
-Original Message-
From: Abdelatif Guettouche
Sent: den 19 oktober 2020 12:05
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule
Thanks Brennan! That was a lot of work!
On Mon, Oct 19, 2020 at 6:25 AM Brennan Ashton
wrote:
>
> On Sa
Thanks Brennan! That was a lot of work!
On Mon, Oct 19, 2020 at 6:25 AM Brennan Ashton
wrote:
>
> On Sat, Oct 17, 2020 at 6:37 AM Abdelatif Guettouche
> wrote:
> >
> > Thanks for merging, Brennan!
> >
> > I'll work on some more today.
> > It'd be great if others can help, there are 515 PRs left
On Sat, Oct 17, 2020 at 6:37 AM Abdelatif Guettouche
wrote:
>
> Thanks for merging, Brennan!
>
> I'll work on some more today.
> It'd be great if others can help, there are 515 PRs left :D
> In any case, here are the links:
> Github Project: https://github.com/apache/incubator-nuttx/projects/7
> R
Thanks for merging, Brennan!
I'll work on some more today.
It'd be great if others can help, there are 515 PRs left :D
In any case, here are the links:
Github Project: https://github.com/apache/incubator-nuttx/projects/7
Releases notes: https://cwiki.apache.org/confluence/display/NUTTX/NuttX+10.0
Thanks for starting the cards and opening the backports. Now that the
weekend is here I'll see what I can do to try to close out a bunch of the
cards as well.
I also want to pick up where I left off testing last weekend. Hopefully we
can cut an RC Sunday or Monday at the latest.
--Brennan
On Sat
Can someone please merge the backport PRs?
Brennan, now that the cards are in place, we will continue sorting
them as we did last time? I added some minor PRs to their column the
other day.
On Wed, Oct 14, 2020 at 10:13 PM Abdelatif Guettouche
wrote:
>
> That did the job! Thanks! It looks good
That did the job! Thanks! It looks good.
Looking at the demos, it looks like it's possible to add triage
automation based on labels, is that right?
What do you have in mind for that?
With the help of a CI script or some Github bot we can automatically
apply labels on PRs, maybe by using the PR des
On Tue, Oct 13, 2020, 2:59 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> > Ah. I actually was finishing up scripting to manage this and was going to
> > generate it tonight. It is also capable of syncing the lists and
> generating
> > new boards and letting you see the PR body
> Ah. I actually was finishing up scripting to manage this and was going to
> generate it tonight. It is also capable of syncing the lists and
generating
> new boards and letting you see the PR body while you write the release not
> entry. There are like 600 for this release and I wanted a better w
On Tue, Oct 13, 2020, 2:12 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Hi,
>
> I backported all the PRs that were labeled for backporting. If anyone
> can take a look and merge them that would be great.
> I created the Release Notes-10.0 board and added some cards there.
>
Hi,
I backported all the PRs that were labeled for backporting. If anyone
can take a look and merge them that would be great.
I created the Release Notes-10.0 board and added some cards there.
The "Minor" column regroups all of the style, typos, grammar like PRs.
Is there a way to automatically a
> I did notice a fair number of patches for bug fixes this week that we may
> want to be applying to this release including the spresense and esp, but
> there may have been others as well. It would be nice if those could be
> backported as needed prior to cutting the RC.
Regarding Xtensa/ESP32, I
I'm a little behind where I wanted to be but I have collected a bunch of
the boards that we support and am going to work through what I can test
with them this weekend.
I did notice a fair number of patches for bug fixes this week that we may
want to be applying to this release including the spres
The releases/10.0 branches have been created off of master for both
apps and the OS.
I will work on populating the release note board tomorrow and starting
to compile them.
If any fixes need to be made for the 10.0.0 release they should be
made against master
and then a new PR made against the rel
I'm still seeing some important changes outstanding and in flux and no real
stability window what do people think about shifting the schedule by 4
days. So the branch would be created on 10/7 (My evening time GMT-7)
instead of 10/3. Having to deal with backports right off the bat is not
really
ess if you want
> > >
> > > Regards
> > > Alin
> > >
> > >
> > > -Original Message-
> > > From: Adam Feuer
> > > Sent: den 23 september 2020 21:13
> > > To: dev@nuttx.apache.org
> > > Subject: Re: [DISCUSS]
ant to help you on the next release process if you want
> >
> > Regards
> > Alin
> >
> >
> > -Original Message-
> > From: Adam Feuer
> > Sent: den 23 september 2020 21:13
> > To: dev@nuttx.apache.org
> > Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedul
ase process if you want
>
> Regards
> Alin
>
>
> -Original Message-
> From: Adam Feuer
> Sent: den 23 september 2020 21:13
> To: dev@nuttx.apache.org
> Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule
>
> Brennan,
>
> Thanks for doing all thi
HI Brennan,
The release schedule looks god.
@Adam Feuer
I want to help you on the next release process if you want
Regards
Alin
-Original Message-
From: Adam Feuer
Sent: den 23 september 2020 21:13
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule
Brennan,
Thanks for doing all this. I'm willing to be release manager for the next
release after 10.0.0.
-adam
On Tue, Sep 22, 2020 at 10:13 PM Brennan Ashton
wrote:
> Hey all, we have talked in loose terms about this release, but I think
> it is time we committed, it has been probably too lo
On Wed, Sep 23, 2020, 7:13 AM Nathan Hartman
wrote:
> On Wed, Sep 23, 2020 at 9:55 AM Matias N. wrote:
> >
> > Ok, I created the "future" milestone for this. We should try to get all
> PRs issues in either
> > of these two milestones during that week.
> >
> > Also, I'm not sure how you're findin
On Wed, Sep 23, 2020 at 9:55 AM Matias N. wrote:
>
> Ok, I created the "future" milestone for this. We should try to get all PRs
> issues in either
> of these two milestones during that week.
>
> Also, I'm not sure how you're finding all PRs for this release to build
> release notes, but one pos
Ok, I created the "future" milestone for this. We should try to get all PRs
issues in either
of these two milestones during that week.
Also, I'm not sure how you're finding all PRs for this release to build release
notes, but one possibility
is to use GH CLI tool. It can be used to list PRs and
On Wed, Sep 23, 2020 at 9:33 AM Matias N. wrote:
> also sounds good. During that week we could take all issues and PRs with
> unassigned
> milestone in GH and assign them to 10.0 or to an "untargeted" or "future"
> release.
> Those with 10.0 milestone should be merged/addressed to include in rel
Hi Brennan,
I can help with the doc versioning in CI since I've partly worked that.
As per the release schedule, sounds right to me. The feature freeze window
also sounds good. During that week we could take all issues and PRs with
unassigned
milestone in GH and assign them to 10.0 or to an "untar
Hey all, we have talked in loose terms about this release, but I think
it is time we committed, it has been probably too long since our last
release.
Here is what I would propose for a release schedule:
09/28/20 -- Master Stability Window (keep the merging of risky PRs
to a minimum this week)
29 matches
Mail list logo
