Hi Sheng, Yes. I do _not_ ask INFRA to support it, but to see if there is existing practice.
Best, tison. Sheng Wu <wu.sheng.841...@gmail.com> 于2022年6月29日周三 19:33写道： > Hi Tison > > I think there is no hard requirement from infra or Apache perspective. The > PMC could decide what they like, and ask Infra team to set them up. > > tison <wander4...@gmail.com>于2022年6月29日 周三19:25写道： > > > Hi, > > > > There're several solutions around GitHub ecosystem to queuing patches > > passed reviews and waiting for merged, especially in case to avoid > semantic > > conflict; e.g., Mergify or Bors-NG. > > > > After enabled branch must be up-to-date with main branch, it introduces > an > > issue that multiple patches can race each other and cause unnecessary CI > > tasks rerun - two patches can be verified simultaneously, after one > merged, > > the other should rerun, which generally cause O(n^2) task instance while > > with queuing only O(n) is required. > > > > Given that there're existing solutions, I'd like to ask what the best > > practice for Apache projects host developments on GitHub on this topic. > Or > > what support does INFRA provide for the certain case. > > > > Best, > > tison. > > > -- > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 >
