The actualization of issue backlog for 2.4.x

[Serhii Dzhepa]

Due to the rules and requirements of this public repository:

We are able to process, collaborate, fix, and deliver pull requests ONLY for Issues that can be reproduced on the latest 2.4-develop public branch.

Proof links:

• Code Contributions: Accepted pull requests and ported code
  Quote

  
  v2.4 Contribution Notice: Magento is focusing development efforts on v2.4, so we are no longer accepting pull requests to the v2.3, v2.2, v2.1, and v2.0 release lines.

• GitHub Issues Processing Workflow: Verification
  Quote

  
  Be advised, we only accept pull requests for 2.4-develop.
  Check if the issue exists on the 2.4-develop branch with a clean installation, configured by described preconditions, following the exact reproduction steps.
  -- If the described behavior was reproduced, the maintainer should apply the Reproduced on 2.4 label to the ticket, indicating that issue was reproduced and specific version.
  -- If the issue was not reproducible with 2.4-develop, the maintainer should close the issue and stop verification process here!

• Issue reporting guidelines this link exists in each new issue report template
  Quote

  
  Checks if the issue exists on the 2.4-develop branch with clean Magento installation. Be advised, we only accept pull requests for 2.4-develop. If the issue is not reproducible on 2.4-develop, it will be closed.

Branch 2.3-develop was removed from the public repository. All fixes to the previous release allowed and can be done ONLY by the Magento team. Based on the prioritized backlog by the Product Management team.
All issue related to the previous Magento versions can be reported only through:

• support channel associated with you magento.com account
• participation in Magento Beta Program

[Serhii Dzhepa]

1. Not triaged; not confirmed Issues
   -- Issues related to “Dev.Experience”

2. Not triaged; Confirmed
   -- Marked as waiting for Dev Triage

3. Not triaged; Confirmed only for “2.3.x”

4. Not triaged; Confirmed on “2.4.x”

[Serhii Dzhepa]

Issues that were confirmed previously on versions before 2.4.x : 538

• has label Confirmed
• does not have the label "Reproduced on: 2.4.x"

[Serhii Dzhepa]

Approach:
Step 1: Issue re-Confirmation on 2.4-develop

1. remove Confirmed label
2. Remove ALL Repro Labels
3. set some cleanup lable: "Need re-check on 2.4"
4. All issue should be commented:

This issue should be re-checked on the lates 2.4-develop branch
If its can be reproduced on 2.4-develop it should be confirbed as still actual
If its cannot be repro on 2.4-develop(only on 2.2.x or 2.3.x) it should be closed due to rules,
Please see The actualization of issue backlog for 2.4.x (#1)

5. Unlink with Jira tickets(to avoid integration bugs)
6. MB close jira tickets????

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.