[ https://issues.apache.org/jira/browse/FLINK-35602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weijie Guo updated FLINK-35602: ------------------------------- Attachment: (was: screenshot-1.png) > [Umbrella] Test Flink Release 1.20 > ---------------------------------- > > Key: FLINK-35602 > URL: https://issues.apache.org/jira/browse/FLINK-35602 > Project: Flink > Issue Type: Improvement > Components: Tests > Affects Versions: 1.20.0 > Reporter: Weijie Guo > Priority: Blocker > Attachments: screenshot-3.png > > > This is an umbrella ticket for the Flink 1.20 testing efforts. > There're two kinds of ticket: 'Release Testing Instructions' and 'Release > Testing' ones. > Release Testing Instructions > For the Release Testing Instructions ticket (title starts with 'Release > Testing Instructions:', > please follow the steps: > 1. Whether the feature needs a crossteam testing, if no, authors just close > the ticket > 2. If testing is required, the author should prepare user document[must have] > and additional instructions (if exists, which are thought necessary for > testers, e.g., some limitations that are outside the scope of the design) > 3. After No.2 is done, the author should close the jira and clone/create a > new jira for tracking the testing result(keep unassigned or assign to a > volunteer) > Other features need cross-team testing > Also contributors are encouraged to create tickets if there are other ones > that need to be cross-team tested (Just create new ticket for testing using > title 'Release Testing: Verify ...' without 'Instructions' keyword). > Release Testing > Note: All the testing sub-tasks should be opened with: > Priority: Blocker > Fix Version: 1.19.0 > Label: release-testing -- This message was sent by Atlassian Jira (v8.20.10#820010)