Unfortunately, consuming the committers' fork repo isn't a good idea because I'm already struggling with resource limitations when creating my own PRs.
This idea will severely hurt the productivity of all active Apache Spark committers. In addition, Apache Spark main repository will also block all Apache Spark sister projects (Apache Spark K8s Operator and Apache Spark Swift Connector) contributions, too. In other words, technically the donor will end up as a zombie unable to create any OSS PRs. Sincerely, Dongjoon. On 2026-10-28 16:36 UTC Hyukjin Kwon wrote: > Hi all, > > We're facing resource issues in CI. More than 50% is from the post builds. > I have an idea to leverage committers' fork when they merge, triggering a > job in committers fork repo. The capacity might be an issue. WDYT about it? > > Otherwise, I think another feasible approach is to only run the build > against the latest commit (and cancel others). > --------------------------------------------------------------------- To unsubscribe e-mail: [email protected]
