**beam-site** is there for legacy reasons I suppose we can remove them without any consequence. Most of the history is in the other repo and the actual site in the master branch.
**runners-spark2** I think we can go ahead and remove it, this was the in-progress work of Amit Sela who has not been active in the project for a while, we already have support for Spark 2 and even for Spark 3 with both the old and the new Spark APIs so most of the features of that branch should be covered and if they are not they should be quite hard to migrate to the actual codebase (e.g. the portable runner was not around, as well as the multiple runner implementations). The other runners are arguable useful for reference but not based in the new Runner/Fn APIs and clearly un-maintained, they are based on Beam versions 4-5y old so I would also think we should maybe remove them, or do a vote for removal of the branches. It is not that the branches are a problem but they are probably not that useful too. Ismaël Ismaël On Fri, Feb 4, 2022 at 5:52 PM Kenneth Knowles <[email protected]> wrote: > > Hi all, > > I was cleaning up branches on the main repo like a lot of "patch" and > "revert" branches that GitHub creates through the UI. I noticed the following > branches that represent real work and I was thinking about adding them to the > list of "protected" branches so they cannot be accidentally deleted: > > * beam-site > * runners-spark2 > * tez-runner > * mr-runner > * jstorm-runner > > Now, I know that the last three are very very old but I think it is harmless > to keep them around. But I wonder if the top two are entirely obsolete now. > They have not been updated in a very long time. Does anyone know? > > Kenn
