[
https://issues.apache.org/jira/browse/FLINK-33826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-33826:
----------------------------
Summary: Triage release-blocking issues in JIRA (was: CLONE - Triage
release-blocking issues in JIRA)
> Triage release-blocking issues in JIRA
> --------------------------------------
>
> Key: FLINK-33826
> URL: https://issues.apache.org/jira/browse/FLINK-33826
> Project: Flink
> Issue Type: Sub-task
> Reporter: Jing Ge
> Assignee: Jing Ge
> Priority: Major
>
> https://issues.apache.org/jira/projects/FLINK/versions/12353640
> There could be outstanding release-blocking issues, which should be triaged
> before proceeding to build a release candidate. We track them by assigning a
> specific Fix version field even before the issue resolved.
> The list of release-blocking issues is available at the version status page.
> Triage each unresolved issue with one of the following resolutions:
> * If the issue has been resolved and JIRA was not updated, resolve it
> accordingly.
> * If the issue has not been resolved and it is acceptable to defer this
> until the next release, update the Fix Version field to the new version you
> just created. Please consider discussing this with stakeholders and the dev@
> mailing list, as appropriate.
> ** When using "Bulk Change" functionality of Jira
> *** First, add the newly created version to Fix Version for all unresolved
> tickets that have old the old version among its Fix Versions.
> *** Afterwards, remove the old version from the Fix Version.
> * If the issue has not been resolved and it is not acceptable to release
> until it is fixed, the release cannot proceed. Instead, work with the Flink
> community to resolve the issue.
>
> ----
> h3. Expectations
> * There are no release blocking JIRA issues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
