[
https://issues.apache.org/jira/browse/FLINK-32923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl updated FLINK-32923:
----------------------------------
Description:
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
was:
For user facing features that go into the release we'd like to ensure they can
actually _be used_ by Flink users. To achieve this the release managers ensure
that an issue for cross team testing is created in the Apache Flink Jira. This
can and should be picked up by other community members to verify the
functionality and usability of the feature.
The issue should contain some entry points which enables other community
members to test it. It should not contain documentation on how to use the
feature as this should be part of the actual documentation. The cross team
tests are performed after the feature freeze. Documentation should be in place
before that. Those tests are manual tests, so do not confuse them with
automated tests.
To sum that up:
* User facing features should be tested by other contributors
* The scope is usability and sanity of the feature
* The feature needs to be already documented
* The contributor creates an issue containing some pointers on how to get
started (e.g. link to the documentation, suggested targets of verification)
* Other community members pick those issues up and provide feedback
* Cross team testing happens right after the feature freeze
----
h3. Expectations
* Jira issues for each expected release task according to the release plan is
created and labeled as \{{{}release-testing{}}}.
* All the created release-testing-related Jira issues are resolved and the
corresponding blocker issues are fixed.
> Triage release-blocking issues in JIRA
> --------------------------------------
>
> Key: FLINK-32923
> URL: https://issues.apache.org/jira/browse/FLINK-32923
> Project: Flink
> Issue Type: Sub-task
> Reporter: Sergey Nuyanzin
> Priority: Major
>
> 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)
