[
https://issues.apache.org/jira/browse/FLINK-33841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33841:
----------------------------
Description:
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}
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
was:
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}
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)
> Create Git tag and mark version as released in Jira
> ---------------------------------------------------
>
> Key: FLINK-33841
> URL: https://issues.apache.org/jira/browse/FLINK-33841
> Project: Flink
> Issue Type: Sub-task
> Reporter: Jing Ge
> 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}
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
