You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/03/22 11:07:00 UTC
[jira] [Updated] (FLINK-31565) Create Git tag and mark version as released in Jira
[ https://issues.apache.org/jira/browse/FLINK-31565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl updated FLINK-31565:
----------------------------------
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}
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)
was:
Create and push a new Git tag for the released version by copying the tag for the final release candidate, as follows:
{code}
$ 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.
> Create Git tag and mark version as released in Jira
> ---------------------------------------------------
>
> Key: FLINK-31565
> URL: https://issues.apache.org/jira/browse/FLINK-31565
> Project: Flink
> Issue Type: Sub-task
> Reporter: Matthias Pohl
> 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)