You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/07/09 08:43:00 UTC

[jira] [Assigned] (FLINK-9747) Release guide ambigous regarding release branches

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

Chesnay Schepler reassigned FLINK-9747:
---------------------------------------

    Assignee: Chesnay Schepler

> Release guide ambigous regarding release branches
> -------------------------------------------------
>
>                 Key: FLINK-9747
>                 URL: https://issues.apache.org/jira/browse/FLINK-9747
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>
> The release guide contains a dedicated section to [Create a release branch|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release#CreatingaFlinkRelease-Createareleasebranch].
> Yet, the first step in the [Build a release candidate|https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release#CreatingaFlinkRelease-Buildareleasecandidate] is to create another release branch.
> {code}
> Now, create a release branch:
> $ cd tools
> tools $ OLD_VERSION=$CURRENT_SNAPSHOT_VERSION NEW_VERSION=$RELEASE_VERSION RELEASE_CANDIDATE=$RC_NUM releasing/create_release_branch.sh
> {code}
> We should use different terms, as the first is about _snapshot_-release-branches (like release-1.5), the latter about the branches actually used for a specific release (like release-1.5.0-rc1).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)