Indeed, retirement is not the death of a project, but rather one way to exit the Incubator. There is no shame in it. The ASF isn’t the best fit for every project.
Thanks for info, I wasn't aware of what retiring meant, I assumed (incorrectly) that retiring = death of a project.
(On behalf of Gearpump runner)
Getting retired (from Apache) doesn't mean the end of Gearpump as a project but to make it easier to commit and release for, honestly speaking, a small community.
I've been maintaining Gearpump runner and will strive for better integration here.
I agree we should revisit this question if the runner is too much of a burden.
Datatorrent the largest contributor to the Apex project has closed shop, the project hasn't retired but development has significantly slowed down. The Gearpump project has voted to retire.
Do people know if these runners are being used?
Do people spend enough time on supporting/updating code in these areas or looking at test flakes that warrant supporting them still?
Are there other runners in a similar situation as to Apex or Gearpump?
Should we revisit this question once we have a larger integration that we want to do like SplittableDoFn or portability?