[
https://issues.apache.org/jira/browse/FLINK-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283602#comment-17283602
]
Robert Metzger commented on FLINK-9747:
---------------------------------------
I don't think this is too much of a problem. This has been reported more than 2
years ago, but nobody else seemed to have stumbled across this. I'm closing
this ticket. Please reopen if you disagree.
> Release guide ambigous regarding release branches
> -------------------------------------------------
>
> Key: FLINK-9747
> URL: https://issues.apache.org/jira/browse/FLINK-9747
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Reporter: 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
(v8.3.4#803005)
