[
https://issues.apache.org/jira/browse/FLINK-33828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge closed FLINK-33828.
---------------------------
Assignee: Jing Ge (was: Qingsheng Ren)
Resolution: Won't Fix
> No need - Cross team testing
> ----------------------------
>
> Key: FLINK-33828
> URL: https://issues.apache.org/jira/browse/FLINK-33828
> Project: Flink
> Issue Type: Sub-task
> Reporter: Jing Ge
> Assignee: Jing Ge
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
