I was thinking about this but there are several concerns -there is no traceability on Nuttx -the bulk PR is impossible to review before merging
Best Regards Alin J On Sat, 31 Oct 2026, 12:37 Alan C. Assis, <[email protected]> wrote: > I think we need to find some alternatives, because the volume of bp-xxxx is > very high. > > Maybe you should merge all the commits in your branch and submit them as > groups of bp containing many of the original PRs. > > This way the group of PRs will be tested outside of apache/nuttx GitHub > before being submitted there. > > BR, > > Alan > > On Sat, Oct 31, 2026 at 8:25 AM Alin Jerpelea <[email protected]> wrote: > > > I am cherry picking bugfixes and security vulnerabilities for every > release > > in the stabilization phase. > > > > Please note that this time we have over 300 fixes due to the enhanced AI > > assisted productivity. > > > > I know that CI is under pressure but we still need to test and merge only > > after the patches complete succesfully the CI check > > > > If you have other suggestions please provide them here > > > > Best regards > > Alin J > > > > > > On Sat, 31 Oct 2026, 10:01 Xiang Xiao, <[email protected]> > wrote: > > > > > Alin and community, > > > I would suggest that we only cherry-pick the critical fix to the > release > > > branch, because: > > > > > > 1. The new patch may contain bug > > > 2. Waste CI and maintainer resource > > > > > > > > > Thanks > > > Xiang > > > > > >
