[
https://issues.apache.org/jira/browse/FLINK-41130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuepeng Pan updated FLINK-41130:
--------------------------------
Description:
This is an umbrella ticket for the Flink 2.4 testing efforts.
There're two kinds of ticket: 'Release Testing Instructions' and 'Release
Testing' ones.
h2. Release Testing Instructions
For the Release Testing Instructions ticket (title starts with 'Release Testing
Instructions:',
please follow the steps:
!image-2026-10-25-01-21-48-174.png!
1. Whether the feature needs a crossteam testing, if not, authors just close
the ticket
2. If testing is required, the author should prepare user document [must have]
and additional instructions (if any, 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)
h3. Other features need cross-team testing
Contributors are encouraged to create additional tickets if there are other
things that need to be cross-team tested (Just create new ticket for testing
using title 'Release Testing: Verify ...' without 'Instructions' keyword).
h2. Release Testing
Note: All the testing sub-tasks should be opened with:
Priority: Blocker
Fix Version: 2.4.0
Label: release-testing
was:
This is an umbrella ticket for the Flink 2.4 testing efforts.
There're two kinds of ticket: 'Release Testing Instructions' and 'Release
Testing' ones.
h2. Release Testing Instructions
For the Release Testing Instructions ticket (title starts with 'Release Testing
Instructions:',
please follow the steps:
!image-2026-04-16-20-52-46-518.png!
1. Whether the feature needs a crossteam testing, if not, authors just close
the ticket
2. If testing is required, the author should prepare user document [must have]
and additional instructions (if any, 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)
h3. Other features need cross-team testing
Contributors are encouraged to create additional tickets if there are other
things that need to be cross-team tested (Just create new ticket for testing
using title 'Release Testing: Verify ...' without 'Instructions' keyword).
h2. Release Testing
Note: All the testing sub-tasks should be opened with:
Priority: Blocker
Fix Version: 2.4.0
Label: release-testing
> [Umbrella] Test Flink Release 2.4
> ---------------------------------
>
> Key: FLINK-41130
> URL: https://issues.apache.org/jira/browse/FLINK-41130
> Project: Flink
> Issue Type: Improvement
> Reporter: Yuepeng Pan
> Priority: Major
> Attachments: image-2026-10-25-01-21-48-174.png
>
>
> This is an umbrella ticket for the Flink 2.4 testing efforts.
> There're two kinds of ticket: 'Release Testing Instructions' and 'Release
> Testing' ones.
> h2. Release Testing Instructions
> For the Release Testing Instructions ticket (title starts with 'Release
> Testing Instructions:',
> please follow the steps:
> !image-2026-10-25-01-21-48-174.png!
> 1. Whether the feature needs a crossteam testing, if not, authors just close
> the ticket
> 2. If testing is required, the author should prepare user document [must
> have] and additional instructions (if any, 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)
> h3. Other features need cross-team testing
> Contributors are encouraged to create additional tickets if there are other
> things that need to be cross-team tested (Just create new ticket for testing
> using title 'Release Testing: Verify ...' without 'Instructions' keyword).
> h2. Release Testing
> Note: All the testing sub-tasks should be opened with:
> Priority: Blocker
> Fix Version: 2.4.0
> Label: release-testing
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
