On Wed, Mar 8, 2023 at 5:37 PM Lwazi Dube <lwa...@gmail.com> wrote: > On Wed, 8 Mar 2023 at 09:55, Alan C. Assis <acas...@gmail.com> wrote: > > > > Sebastien, > > > > If all the discussions that happens on github start to happen here, > > this mailing list will be just like the nuttx-commits mailing list. > > I'll take this as sarcasm. Sebastien is making a lot of valid points, > in good faith, and being dismissive does not help the community.
Folks, this seems to be getting personal, please stop, make a point, suggest a solution, lets make it happen in a good old fashioned and calm way, please :-) Some interesting news (some of them really sad) showed up, and review process suggestions has been made. I am using BSD Unix not Linux because I do not like enforced changes and I know that things from 10 years back will still work here and will work in next 10 years. This discussion is somehow about "enforced changes"^TM too. This comes from Linux world and I think more and more people will turn back on Linux because of this (I did this around 2008 when kernel api started changing every minor release). I like NuttX because there are no enforced changes here and I would love things to stay that way. In a perfect situation code that runs on a release 9 should also work on a release 13. Lets stay "self compatible" :-) Master branch can have some things that will not work. No one is able to predict everything. It is still possible to revert changes or redirect them in a good "backward compatible" way with a new feature. I was also surprised by a silent build, but that did not push me to swear on a mailing list :-) I like the reaction of the community here with a constructive solution proposition to make this silent build optional. Things will work as usual, but new functionality will be available. What is the problem? We still have some time before a next release. Lets use that critics to make a constructive solution and keep discussions elegant :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
