On Thu, Jan 30, 2025 at 2:39 PM Tomek CEDRO wrote:
> Thank you Xiang!! :-) Would it be possible to support Lup's work too
> in this area? Lup saved our GitHub CI and has amazing results already
> with working prototype of independent distributed build and runtime
> testing :-)
> Tomek
>
>
we alre
Hi!
LTS releases is a good idea as such, but the underlying problem which
Sebastien is (sort of..) pointing out needs to be addressed somehow also
in the mainline.
I get frustrated as well, from time to time, with a huge amount of
unnecessary commits being pushed in, very quickly. I will jus
so thats how it's going to happen?
One small email from one of the one company that causes most of the
problem, no discussion, and that is done?
Think about that once again.
My idea at this stage is quite different.
Every large company wanting to push many commits into nuttx should have
a
Hello
On 1/30/25 08:05, Tomek CEDRO wrote:
For instance if Sebastien had his board attached to local CI machine
that builds and runs the master all the time it would be really easy
and quick to catch possible problems and fix them right away not after
one year. It may be even possible to catch c
On Thu, Jan 30, 2025 at 1:42 AM Nathan Hartman wrote:
> On Wed, Jan 29, 2025 at 3:40 PM Alin Jerpelea wrote:
> > LTS is a good idea the only issue is that we can not guarranty that the
> > patches can be backported for 2 years due to the way PRs are submitted.
> > most time a change is affecting
Thank you Xiang!! :-) Would it be possible to support Lup's work too
in this area? Lup saved our GitHub CI and has amazing results already
with working prototype of independent distributed build and runtime
testing :-)
Tomek
On Thu, Jan 30, 2025 at 6:41 AM Xiang Xiao wrote:
>
> Ok, let's come up
Ok, let's come up with a solid plan. Xiaomi could sponsor
engineering resources to improve the community automation test quality.
On Thu, Jan 30, 2025 at 12:50 PM Nathan Hartman
wrote:
> That's true. So we should:
>
> 1. Decide if we want to have a LTS release, and
>
> 2. If yes, then we need to
That's true. So we should:
1. Decide if we want to have a LTS release, and
2. If yes, then we need to determine all the prerequisites. That will
include things like the solid automation tests, and probably other things
3. Once we have defined what is needed, we can track the items in the issue
t
Before we have a solid automation test, how do we declare the release is
good enough to be LTS release?
As I mentioned before, it's impossible to have a stable base or LTS release
without enough automation test.
On Thu, Jan 30, 2025 at 4:05 AM Nathan Hartman
wrote:
> On Wed, Jan 29, 2025 at 8:21
On Wed, Jan 29, 2025 at 3:40 PM Alin Jerpelea wrote:
>
> LTS is a good idea the only issue is that we can not guarranty that the
> patches can be backported for 2 years due to the way PRs are submitted.
> most time a change is affecting multiple drivers or subsistems instead of
> having separate s
LTS is a good idea the only issue is that we can not guarranty that the
patches can be backported for 2 years due to the way PRs are submitted.
most time a change is affecting multiple drivers or subsistems instead of
having separate smaller PRs.
We will need to improve guidelines and do PR screeni
On Wed, Jan 29, 2025 at 8:21 AM Alan C. Assis wrote:
>
> Hi Simon,
>
> Yes, but it important to prove your point using a commercially available
> development board.
>
> NuttX (just like Linux) is a moving target. So one out of tree board always
> will break because people are constantly changing t
> the solution is simple. dont fix what is not broken, even if you really
really really want to optimize something.
But this is an obvious contradiction. If the OS doesn't meet the performance
requirements, then it should be fixed. Maybe this isn't an issue for your
app,
but there are plenty of us
the solution is simple. dont fix what is not broken, even if you really
really really want to optimize something.
also you could have an official "out of tree board" that you keep
working so customers can track these changes.
linux is a moving target but not its build system. There is some t
Hi Simon,
Yes, but it important to prove your point using a commercially available
development board.
NuttX (just like Linux) is a moving target. So one out of tree board always
will break because people are constantly changing the building system and
moving things of place.
There is no simple w
Hi Sebastian,
as a release manager I look forward to get your test results and improve
the release
Best regards
Alin
On Wed, Jan 29, 2025 at 12:51 PM Simon Filgis <
si...@ingenieurbuero-filgis.de> wrote:
> Hi Alin,
>
> thank you. Very fine for me!
>
> Regards,
>
> Simon
>
> Alin Jerpelea schr
Hi Raiden,
I am sorryyou are right.
The initial discussion was initiated on the project management list since
we wanted to align and set the initial targets
We can start a similar thread on dev and then summarize the targets.
Best regards
Alin
On Wed, Jan 29, 2025 at 12:34 PM raiden00pl w
Hi Alin,
thank you. Very fine for me!
Regards,
Simon
Alin Jerpelea schrieb am Mi., 29. Jan. 2025, 12:48:
> Hi Simon,
>
> you can always vote as a community member with -1 and explain what the
> issue is (you can check the last release vote thread)
>
> The release process for each release:
> 1
On 2025-01-29 12:12:58, raiden00pl wrote:
> I completely agree that project management in NuttX is either lacking or
> completely non-existent. I think the lack of a generally accepted road map
> for
> the project is the biggest problem here. TBH we don't even know where
> the project is headed. Pr
Hi Simon,
you can always vote as a community member with -1 and explain what the
issue is (you can check the last release vote thread)
The release process for each release:
1) a release branch created 3-4 weeks before the release. (you can test
your board on it and post bugs in the bug report)
2)
> I started a thread some time ago asking for imput and wishes from all of
us
so that we cans set some goals and create a roadmap
Unfortunately the mail got little tractionmaybe now we can revive it
and complete a roadmap
Was it posted on this list (dev@nuttx)? I don't recall such a thread her
Just for my understanding, could I vote -1 for a release that is not
building/working properly for my board?
Alin Jerpelea schrieb am Mi., 29. Jan. 2025, 12:24:
> Hi all,
>
> I started a thread some time ago asking for imput and wishes from all of us
> so that we cans set some goals and create a
I completely agree that project management in NuttX is either lacking or
completely non-existent. I think the lack of a generally accepted road map
for
the project is the biggest problem here. TBH we don't even know where
the project is headed. Probably if this large number of commits were
supporte
Hi all,
I started a thread some time ago asking for imput and wishes from all of us
so that we cans set some goals and create a roadmap
Unfortunately the mail got little tractionmaybe now we can revive it
and complete a roadmap
Best regards
Alin
On Wed, 29 Jan 2025, 12:14 raiden00pl, wrote:
hi
On 29/01/2025 10:21, raiden00pl wrote:
Sebastian, so you're saying that you and your company have the resources to
develop
and maintain your own RTOS, but you lack the resources to help maintain
NuttX (e.g., code review, release testing.)?
This either doesn't make sense or you just don't wan
On 2025-01-28 11:23:26, Sebastien Lorquet wrote:
> my trust in nuttx is now hard to maintain.
>
> Every day a DELUGE of commits (from xiaomi, this is a fact) is added to the
> repository.
>
> I am struggling to understand what happens in this project.
>
> so many fixes are pushed, how is that ev
Sebastian, so you're saying that you and your company have the resources to
develop
and maintain your own RTOS, but you lack the resources to help maintain
NuttX (e.g., code review, release testing.)?
This either doesn't make sense or you just don't want to participate in
this project.
Cherry-pick
On Tue, Jan 28, 2025 at 11:23 AM Sebastien Lorquet wrote:
> my trust in nuttx is now hard to maintain.
> Every day a DELUGE of commits (from xiaomi, this is a fact) is added to
> the repository.
> I am struggling to understand what happens in this project.
> so many fixes are pushed, how is that e
Hi Sebastien,
This is the last time that I will eat the bait!
I agree that all commits should have some proper git commit message and
that is something that normally I always ask for!
And as others already commented this is part of a bigger PR and this
specific commit is very intuitive.
So, inst
29 matches
Mail list logo
