[jira] [Assigned] (FLINK-34712) CLONE - Update reference data for Migration Tests

["lincoln lee (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-34712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lincoln lee reassigned FLINK-34712:
-----------------------------------

    Assignee: lincoln lee  (was: Sergey Nuyanzin)

> CLONE - Update reference data for Migration Tests
> -------------------------------------------------
>
>                 Key: FLINK-34712
>                 URL: https://issues.apache.org/jira/browse/FLINK-34712
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Sergey Nuyanzin
>            Assignee: lincoln lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.0, 1.18.1
>
>
> Update migration tests in master to cover migration from new version. Since 1.18, this step could be done automatically with the following steps. For more information please refer to [this page.|https://github.com/apache/flink/blob/master/flink-test-utils-parent/flink-migration-test-utils/README.md]
>  # {*}On the published release tag (e.g., release-1.16.0){*}, run 
> {panel}
> {panel}
> |{{$ mvn clean }}{{package}} {{{}-Pgenerate-migration-test-data -Dgenerate.version={}}}{{{}1.16{}}} {{-nsu -Dfast -DskipTests}}|
> The version (1.16 in the command above) should be replaced with the target one.
>  # Modify the content of the file [apache/flink:flink-test-utils-parent/flink-migration-test-utils/src/main/resources/most_recently_published_version|https://github.com/apache/flink/blob/master/flink-test-utils-parent/flink-migration-test-utils/src/main/resources/most_recently_published_version] to the latest version (it would be "v1_16" if sticking to the example where 1.16.0 was released). 
>  # Commit the modification in step a and b with "{_}[release] Generate reference data for state migration tests based on release-1.xx.0{_}" to the corresponding release branch (e.g. {{release-1.16}} in our example), replace "xx" with the actual version (in this example "16"). You should use the Jira issue ID in case of [release]  as the commit message's prefix if you have a dedicated Jira issue for this task.
>  # Cherry-pick the commit to the master branch. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)