On Wed, Mar 8, 2023 at 11:31 PM Gregory Nutt wrote: > Related: This would be an issue for people who have to support a product > for an extended life. In the early 2010's, for example, there were > products using NuttX based on MCUs with 32Kb of FLASH memory. I suspect > those would already be in trouble. > > The moral of this is: If you have to support the same hardware for > years and years, you really need to freeze the OS version and backport > any critical fixes as necessary.
..and for retro computer folks that want to bring new life to old machines with a recent version of NuttX would be lost.. old is not always bad :-) > >> Maybe, like FreeBSD, we should declare support "tiers" for different > >> architectures and MCUs, with Tier 1 meaning supported fully and other tiers > >> for things like partial support (experimental?) or deprecated... just a > >> thought. > > Good idea... but I doubt that we could ever staff this. It could be simply implemented by assigning "maintainers" to a given platform / application / code, like FreeBSD Ports do :-) In general, person mostly interested in particular application and/or hardware voluntarily applies to be "maintainer" of this specific part of code / application / drivers (probably the author). Then all questions / updates / requests / flames are directed towards that person as the guru knowing the subject best. When person is not interested in maintaining anymore, then another maintainer is being searched, while the part of the code is marked as maintained by the community and supervised by the port tree maintainers team. Maybe there can be tags used in the code comments that would automate status generation in the doc/web. Commits and changes introduced to a specific "port" must be approved by its "maintainer" in the first place. Then they can be verified and committed to the source tree by "port tree maintainers" if the update is fine, or request a fix with hints on how to fix. That split of duties allows adding and updating single ports by less experienced users that are only interested in a specific change (i.e. application update), and it is then verified by people that are most experienced with the whole port tree organization. This is usually done with Bugzilla but I can see it may happen over GitHub too. https://bugs.freebsd.org/bugzilla/buglist.cgi?chfield=%5BBug%20creation%5D&chfieldfrom=24h&list_id=591118 https://github.com/freebsd/freebsd-ports/pulls?q=is%3Apr Working with kernel is similar, but all changes need to be carefully explained and reviewed and approved by several "core team members" (usually at least three) before commit. I think this is done with Phabricator but it may happen over GitHub too. https://github.com/freebsd/freebsd-src/pulls?q=is%3Apr > Slightly different topic: I have almost every board that ever ran NuttX > from about 2005 through 2020 or so. That is probably several hundred > boards. I don't use them any more and am thinking about just dumping > them to make space. Is there anyone willing to pay the shipping from > Costa Rica on a massive dump of older but interesting hardware? TREASURES!! =) What would be the cost??? Priv plz plz :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
