Repository navigation
Branches #539
Description
Activity
There was such a branch (still there as the V5_dev) however there was significant push back from the community so it hasn't gone further. The bulk of activity is on ports to specific silicon rather than the core framework itself. Ideally Each of those would be done in their own repository, keeping a clean separation between the framework and any particular HAL/PAL implementation. Unfortunately the current build system design makes that difficult. Since common code for silicon is in one folder and code specific to a total system (aka Board Support Package) is in another and currently those all reside under the same root as the core runtime itself. Thus even git sub modules don't really work. I'd be happy to see someone wanting to take that on.
The pending requests are pending because the build doesn't completely succeed and no-one has stepped up to fix that. Most of them would be good to go once that is resolved. #486 is really large with numerous comments and concerns so wouldn't go in as-is.
I'm a little surprised to not see any kind of upcoming release branch. Ideally some objectives would be set/agreed for the next release and a branch created. Contributors would fetch this branch and have it locally and on their forks. Then contributors would create pull requests from this next release branch on their forks to the next release branch in this repo.
How do you define and prepare for any next release currently? (I saw a lot of pending pull requests that seem to be lingering, going nowhere).