+1 good idea. If the upstream project is not updating then most likely this can be archived/removed.
We did this for Apex and Gearpump without waiting for a major version bump. Here is that old thread: https://lists.apache.org/thread/p63nbgb6hx0rl8287zjt6q96zwwrtqmr Kenn On Fri, Jun 27, 2025 at 9:23 AM Yi Hu via user <u...@beam.apache.org> wrote: > Hi Joey, > > Thanks for raising this question. As far as I know there are a few tests > exercising on twister2 runner: > > - > https://github.com/apache/beam/actions/workflows/beam_PostCommit_Java_ValidatesRunner_Twister2.yml > - > https://github.com/apache/beam/actions/workflows/beam_PostRelease_NightlySnapshot.yml?query=event%3Aworkflow_dispatch++. > The latter one is part of release validation workflows, which means > itshould work on the latest Beam release at least for basic features > exercised by these tests. > > However there is indeed a proposal to decommission unmaintained runners in > the next major release (Beam 3), for example > https://github.com/apache/beam/issues/35448. Given the status of upstream > trepo, twister2 runner could also be in scope. Feel free to raise a GitHub > Issue for proposal. > > Best, > > Yi > > On Fri, Jun 27, 2025 at 11:58 AM Joey Tran <joey.t...@schrodinger.com> > wrote: > >> Hi, >> >> I was just wondering if twister2 and the twister2runner are still >> maintained or used? >> >> The twister2 repo [1] hasnt seen a change in 5 years and the twister2 >> runner directory has had a similarly low level of activity [2] >> >> [1]https://github.com/cylondata/twister2 >> [2] >> https://github.com/apache/beam/tree/6b06823fcd04a9fe4da26df712bebcec526ad1d5/runners/twister2/src/main/java/org/apache/beam/runners/twister2 >> >
