Bump openvinotoolkit/openvino/.github/workflows/cleanup_dependabot_branches.yml from f77c1e9b6d9e746a816c1a20182917f2c327cc7c to 721ad7a79822ac98320674d73f73a04e10463cfb

[dependabot]

Bumps openvinotoolkit/openvino/.github/workflows/cleanup_dependabot_branches.yml from f77c1e9b6d9e746a816c1a20182917f2c327cc7c to 721ad7a79822ac98320674d73f73a04e10463cfb.

Changelog

Sourced from openvinotoolkit/openvino/.github/workflows/cleanup_dependabot_branches.yml's changelog.

OpenVINO Release Management

The process described below reflects the approach to managing OpenVINO releases.

Release Milestones

• Planning
• Execution (development of new features)
• Stabilization (Feature Freeze, Code Freeze milestones)
• Validation
• Distribution

Planning

This phase takes 2-4 weeks and involves scoping the backlog, prioritizing it, analyzing, and making commitments by developers for timelines specified by the release manager.

Execution (development of new features)

• OpenVINO Contributing Guide
• Code Contribution Guide
• OpenVINO First Good Issue

Stabilization (Feature Freeze, Code Freeze milestones)

• Feature Freeze: This milestone ensures that no new features are added to the software after a certain point. This allows the development team to focus on stabilizing and refining the existing features, fixing bugs, and improving performance without the risk of introducing new issues.
• Code Freeze: This milestone marks the point where no new code changes are allowed except for critical bug fixes. This helps in ensuring that the final product is stable and reliable, as it minimizes the risk of last-minute changes that could introduce new bugs or instability.

Release Validation

• This is a continuous process executed on a regular basis with cadence based on testing type: nightly, bi-weekly, weekly.
• After Code Freeze, the testing team can perform final regression testing to ensure that recent changes have not introduced new bugs and that the software meets the required quality standards.

Distribution

• OpenVINO has different types of build distribution: Regular releases, Long-Term Support, Pre-release releases, Nightly builds. Read more here: OpenVINO Release Policy
• Different distribution channels are supported. Explore different options here: OpenVINO Download

Commits

• 721ad7a [GPU] Sliding window support for non-PA SDPA (#38167)
• 5a6f1d6 [GPU] enable_profiling when ONEDNN_VERBOSE is on (#38840)
• 365c44d Revert "[Transformations][PagedAttention] Replace attention_mask used for bro...
• 3f4d1ba [GPU] Support incomplete user events in SYCL runtime (#38677)
• b321dae [GPU] enable onednn conv for more cases via support byxf layout (#38391)
• a2b94ec [GPU] adding _parent_buffer to ze gpu_usm (#38709)
• 9bc67ea [GPU][MLIR] Add MLIR-converter for grouped-matmul op (#38782)
• 300a354 [NPU] CiP Engineering drop WW42.1 (#38783)
• 7d81aad [GPU] Add stream recording with Level Zero regular command list (#37255)
• 1bb274d [GPU][NPU] Fix zero_loader export (#38665)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)