Sounds like great plan to me. Just wanted to mention one caveat. Non-committers do not have access to ASF CI. I do not think this will change. While no one of us ever said no to push a patch for testing, it is good to have a good backup plan people can do it themselves. Currently this is CircleCI. Maybe we can leave it just as is at some point and people who want to use it can continue supporting it themselves? I don’t have a clear answer now. I guess time will show
On Thu, 20 Oct 2022 at 14:51, Brandon Williams <dri...@gmail.com> wrote: > On Thu, Oct 20, 2022 at 1:45 PM Josh McKenzie <jmcken...@apache.org> > wrote: > > > > My high level hope is that we can: > > > > 1. Unstick mainline yearly releases (vote to accept circle results, make > circle more robust <- WE ARE HERE) > > 2. Invest resources into the ASF CI environment to get it to being a > viable replacement for circle (requirements for this qualification TBD) > > 3. Deprecate circle > > > > I'm doing my best to help make the above a reality. There's a lot of > hand-waving in "ASF CI as viable replacement" but it's 2022 and there's a > lot of modern build and ci system's learning our industry has gained in the > last decade we're not yet taking advantage of. > > I'm a strong +1 on this plan and will do everything I can to assist. > We should have a discussion on how to get this accomplished and > delineate the current problems we are facing. >
