[
https://issues.apache.org/jira/browse/FLINK-32930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782094#comment-17782094
]
Matthias Pohl commented on FLINK-32930:
---------------------------------------
[~jingge] is anyone reviewing the changes? I'm just concerned that we're
missing things, e.g. we missed marking the 1.18.0 as released in Jira even
though it should be covered by this issue.
I'm gonna go ahead and mark 1.18.0 as released in Jira. ...to have this
FLINK-32930 fully resolved. I hope that's ok with you
> Create Git tag and mark version as released in Jira
> ---------------------------------------------------
>
> Key: FLINK-32930
> URL: https://issues.apache.org/jira/browse/FLINK-32930
> Project: Flink
> Issue Type: Sub-task
> Reporter: Sergey Nuyanzin
> Assignee: Jing Ge
> Priority: Major
>
> Create and push a new Git tag for the released version by copying the tag for
> the final release candidate, as follows:
> {code:java}
> $ git tag -s "release-${RELEASE_VERSION}" refs/tags/${TAG}^{} -m "Release
> Flink ${RELEASE_VERSION}"
> $ git push <remote> refs/tags/release-${RELEASE_VERSION}
> {code}
> In JIRA, inside [version
> management|https://issues.apache.org/jira/plugins/servlet/project-config/FLINK/versions],
> hover over the current release and a settings menu will appear. Click
> Release, and select today’s date.
> (Note: Only PMC members have access to the project administration. If you do
> not have access, ask on the mailing list for assistance.)
> If PRs have been merged to the release branch after the the last release
> candidate was tagged, make sure that the corresponding Jira tickets have the
> correct Fix Version set.
>
> ----
> h3. Expectations
> * Release tagged in the source code repository
> * Release version finalized in JIRA. (Note: Not all committers have
> administrator access to JIRA. If you end up getting permissions errors ask on
> the mailing list for assistance)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
