[
https://issues.apache.org/jira/browse/BEAM-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777779#comment-16777779
]
Maximilian Michels commented on BEAM-6714:
------------------------------------------
Good question. In this case I knew that the release branch for 2.11.0 had
already been cut before the merge. The more programmatic would be the following:
1. Make sure you have the latest {{release-X}} branch, e.g. {{release-2.11.0}}.
You can do {{git fetch upstream}}, where upstream is the remote tracking the
Beam repo.
2. Run {{git branch -r --contains <commit hash>}}
For example, for your PR:
{noformat}
$ git branch -r --contains ff6dd4cd1a1438f8196ff13a8cb3a8562bbe72a6
upstream/master
{noformat}
There is no release yet, so Fix Version will be the next to-be-released version.
Let's take a commit which is in the {{release-2.11.0}} branch:
{noformat}
$ git branch -r --contains e7128701a4d195a1ba70750b393ecf218989289c
upstream/master
upstream/release-2.11.0
{noformat}
So we know that the commit first entered release 2.11.0.
> Move runner-agnostic code out of FlinkJobServerDriver
> -----------------------------------------------------
>
> Key: BEAM-6714
> URL: https://issues.apache.org/jira/browse/BEAM-6714
> Project: Beam
> Issue Type: Task
> Components: runner-flink, runner-samza, runner-spark
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 7h 20m
> Remaining Estimate: 0h
>
> [FlinkJobServerDriver|https://github.com/apache/beam/blob/master/runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkJobServerDriver.java]
> contains quite a bit of code that is not actually specific to the Flink
> runner. This runner-agnostic code should be shared so that other runners (ie
> Spark) developing portability can leverage it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
