[
https://issues.apache.org/jira/browse/FLINK-34285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee updated FLINK-34285:
--------------------------------
Description:
This is an umbrella ticket for the Flink 1.19 testing efforts.
RM opened a release test instructions ticket for all completed flips, please
follow the steps:
!screenshot-3.png!
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)
RM has created all tickets for completed features listed on the 1.19 wiki page,
and 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).
Note: All the testing sub-tasks should be opened with:
Priority: Blocker
Fix Version: 1.19.0
Label: release-testing
was:
This is an umbrella ticket for the Flink 1.19 testing efforts.
Please follow the steps:
!screenshot-2.png!
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 create a new jira
for tracking the testing result(keep unassigned or assign to a volunteer)
Note: RM will create all tickets for completed features listed on the 1.19
wiki page, and 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).
All the testing sub-tasks should be opened with:
Priority: Blocker
Fix Version: 1.19.0
Label: release-testing
> [Umbrella] Test Flink Release 1.19
> ----------------------------------
>
> Key: FLINK-34285
> URL: https://issues.apache.org/jira/browse/FLINK-34285
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 1.19.0
> Reporter: lincoln lee
> Assignee: lincoln lee
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.19.0
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> This is an umbrella ticket for the Flink 1.19 testing efforts.
> RM opened a release test instructions ticket for all completed flips, please
> follow the steps:
> !screenshot-3.png!
> 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)
> RM has created all tickets for completed features listed on the 1.19 wiki
> page, and 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).
> 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)
