In another thread, it was observed that feature creep has started setting in. As part of the cause of the problem with my attempts at adding WebAssembly package support, I’ve decided to start collecting the good ideas that came from the ranting in that thread.
Features added distract from the features required to reach release 1.0 of Haiku. There’s no QA team yet so setting up buildbots might be a step in that direction. I know that GitHub’s servers have CI scripting for some instruction sets. What is needed for the rest of the instruction sets?
In addition to building we need some way to quantify how well software works on Haiku once it’s built. A test suite that can report regressions would also be quite handy. What do we have for that?
Supported Platforms for Full Driver Support
If we can get a cheap RISC-V SoC based SBC with a graphics architecture that is documented publicly enough to focus on adding complete driver support, should that be the first buildbot to get stem-to-stern, end-to-end, top to bottom support? I chose RISC-V for the cheapness, availability and low power consumption. @X512 , didn’t you just get one of these on AliExpress for $25? Sounds like a good starting place to me! Also, I have some 32-bit ARM SBCs that don’t consume too much power that might be build bot candidates.
Re: RISC-V boards
Was referring to this post.