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 commits from PRs and react
to changes before these are merged! This is how I see distributed
build and runtime 🙂
That is not going to happen. Please, understand that situations here are
very diverse and can be unexpectedly different from what you assume you
know.
NuttX is just a tool for us, not a big project we enjoy messing around
with. I'm working on it alone, half-time. It's annoying when it breaks.
I was very worried when I found that tcp keepalive was broken, because I
knew how annoying it would be to migrate nuttx to a version that would
work. No patch can be done. several files in net/tcp have been
completely rewritten in the last months, with possible dependencies
everywhere in the codebase.
I can not follow the master branch every day, folks. updating nuttx
takes time and costs money. I cant justify that, I dont have the budget,
neither money or time.
We're not doing iot sensors that can afford to have bugs in prod. we're
doing access control in industrial places. Once the product works it is
not updated unless we have a valuable reason to do so. OTA updates are
possible but rare. It's a risk. If I brick a board hundreds of people
will have problems and I may pay penalties.
Once deployed our products are expected to be reliable and stable, and
they dont need that much updates, because the functionalities are
defined in a multi-million dollars tender and dont change.
Also it's not my full time job, we're two guys working on this, one of
us is exclusively doing the apps and I am in charge of the OS. We cant
hire. Also, there is no one to hire, in fact. Juniors cant handle this.
We have tons of project around that nuttx one, which are NOT related to
nuttx.
It's the reality of small industrial companies struggling.
So, I handle the risk of using an open source OS as the basis for our
work, and when it breaks that much in our back, it's really disheartening.
Sebastien
