CeDeROM

Okay, I can understand rationale behind this change, it simplifies stuff, but it is also breaking change as noted by several people, so I marked PR with [BREAKING] tag do...

This is breaking change so we should keep `[BREAKING]` mark both in PR title and commit title so people will easily find it in logs and release messages when they...

This is the point of `[BREAKING]` tag, we discussed it at start of year, there is nothing bad in putting this tag, there is no bad message, it helps quickly...

Look its not a problem of avoiding breaking changes, we need them sometimes, and cannot avoid them. But we should not hide them. Quite opposite we should expose them, even...

I am okay with this code change, no drama ot voting is required as concerns we discussed already, I just want us to follow rule 1.13.9 of https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md in all...

@jerpelea the release notes use github tag to distinguish breaking changes right?

Do you as you please. This requirement is already in Contributing Guide for over 3 months and everyone seems to ignore it :-(

> @cederom please let us to follow the https://www.conventionalcommits.org/en/v1.0.0/ it will simplify use of NuttX commits with standardized tools Okay we may discuss this approach on the dev mailing list...

I sometimes use union with fixed point number (int) and floating point number (double), so the common variable type can be passed over functions in the whole project with a...

True! I do that when both integer and floating point data are used in the same project. But here you are right @raiden00pl users will prefer either one or the...