Release Readiness — CANDIDATE for next SR (vs release/10.0.1xx-sr11)
🛫 Pre-flight mode. Surveying main (== main) against prior SR release/10.0.1xx-sr11. Shows what WOULD ship if we cut the next SR today.
Verdict — 🔴 Not Ready
- [Tier 1] 1 ×
no-fix-yet
- [Tier 2] 2 ×
merged-non-main-only
- [Tier 2] 1 ×
open-on-main
- [Advisory] Candidate mode — main CI is
stale. Re-evaluate after SR cut.
- [Tier 2] Ship check WATCH: Known Build Errors
- [Tier 2] Ship check WATCH: Candidate PR for next SR cut (SR12)
Tracker: net10-sr12 · mode=candidate · branch=main
HEAD: 54ab39ea — Improve CI-fix Azure queue failure diagnostics (#39243)
Generated: 2026-10-10T14:38:06.1353089Z
🕐 Report generated moments ago.
Nightly dogfood feed: ✅ dotnet10 · ci.inflight — latest 10.0.120-ci.inflight.26509.6 built today.
Expected ship date: Tuesday October 13, 2026 — in 3 days (.NET releases ship on the 2nd Tuesday of each month.)
Regression labels: regressed-in-10.0.110, regressed-in-10.0.120 (mode: explicit)
🔴 Blocking — 1 item(s)
| Area |
Details |
Next action |
| 🐞 #39295 — no-fix-yet |
C2 & C5: Content turns blank when dragging a slider or scrolling the mouse wheel on the Mac Catalyst platform. |
Investigate: no fix PR cross-referenced from issue |
🚩 Candidate PR — SR12 cut point (10.0.120)
The Candidate PR promotes a specific main commit as the base for cutting SR12 (10.0.120). The SR branch can't be cut until it merges, so its status gates the whole cycle.
No open Candidate PR yet. When ready to cut SR12, open a PR titled *Candidate* against main selecting the target commit — the SR is cut from its merge commit. 1 non-maintainer *Candidate*-titled PR(s) were excluded as not real cut PRs.
🧹 Cleanup follow-ups — 2 item(s)
These are housekeeping items that should be addressed but do NOT block this release.
| Area |
Details |
Next action |
| 🧹 Bug template lists SR12 version |
No entry matching 10.0.[120..129] found in version-with-bug dropdown on origin/main. Top entries: 11.0.0-rc.1, 11.0.0-preview.7, 11.0.0-preview.6. |
Add the SR12 version (e.g. 10.0.120) to .github/ISSUE_TEMPLATE/bug-report.yml — can land before or shortly after ship. |
| 🧹 Milestone for next cycle (.NET 10 SR13) |
No milestone matching .NET 10 SR13 exists. Once SR12 ships, open issues will have nowhere to roll forward to — but SR12 can ship first. |
Create the milestone before the next cycle begins: gh api repos/dotnet/maui/milestones -f title=".NET 10 SR13" -f state=open |
Recent CI Failure Scanner signals (ci-scan)
Filtered to issues whose **Branch**: <name> body marker matches main (auto-filed by the CI Failure Scanner workflow every 12h). Fresh issues (<24h) are flagged 🆕.
No ci-scan issues target main.
📥 Open Fix PRs Inbound — 1 PR(s)
Fix PRs in flight for regression issues. Land these (or their backports) before ship to close out the regression list.
| Fix PR |
Base |
Regression issue |
Status |
Next action |
| #38638 |
main |
#38619 — [MAUI] J3_Check Window.TitleBar is not reset after changing Window.Pag... |
🔵 OPEN — awaiting main merge |
Watch for merge to main before the SR cut; rerun readiness after the release/...-srN branch is cut to get the exact backport command |
Ship-readiness checks
| Check |
Status |
Details |
Next action |
| Versions.props bump (main → SR12) |
🟢 READY |
origin/main reports 10.0.120 — within expected SR12 range [120..129]. |
No bump needed. |
| Bug template lists SR12 version |
🧹 CLEANUP |
No entry matching 10.0.[120..129] found in version-with-bug dropdown on origin/main. Top entries: 11.0.0-rc.1, 11.0.0-preview.7, 11.0.0-preview.6. |
Add the SR12 version (e.g. 10.0.120) to .github/ISSUE_TEMPLATE/bug-report.yml — can land before or shortly after ship. |
| P/0 release-branch PRs |
🟢 READY |
No open P/0-labelled PRs target this SR branch. |
Continue monitoring. |
| CI Failure Scanner signals |
🟢 READY |
No open ci-scan issues on main (label ci-scan) — scanner has not flagged recurring CI failures. |
Continue monitoring. |
| Known Build Errors |
🟡 WATCH |
1 open Known Build Error issue(s). May explain background CI noise. |
Cross-check against any SR build failures to distinguish accepted-known vs new regressions. |
| Milestone for next cycle (.NET 10 SR13) |
🧹 CLEANUP |
No milestone matching .NET 10 SR13 exists. Once SR12 ships, open issues will have nowhere to roll forward to — but SR12 can ship first. |
Create the milestone before the next cycle begins: gh api repos/dotnet/maui/milestones -f title=".NET 10 SR13" -f state=open |
| Candidate PR for next SR cut (SR12) |
🟡 WATCH |
No open PR matching *Candidate* from a maintainer (OWNER/MEMBER/COLLABORATOR) found on main (1 non-maintainer PR(s) titled 'Candidate' were excluded as not real cut PRs). The Candidate PR is the mechanism that promotes a specific main commit as the SR cut point. |
When ready to cut, open a Candidate PR against main selecting the target main commit for the next SR. |
Release Captain Notes
Add manual notes here. Anything between these begin/end markers is preserved across automated re-runs.
CI Status — overall: stale
| Pipeline |
Verdict |
Latest result |
At/ahead of SR HEAD? |
Build |
| maui-pr |
stale |
succeeded |
❌ stale |
1628270 |
| maui-pr-devicetests |
stale |
failed |
❌ stale |
1628271 |
| maui-pr-uitests |
stale |
failed |
❌ stale |
1628296 |
What's New in SR — 65 commits
- Source PRs included: 70 (see
sr-source-prs.txt)
- Reverts detected: 3
Reverts
Regression Candidates — 4 issues scanned
Summary
| Verdict |
Count |
merged-non-main-only |
2 |
no-fix-yet |
1 |
open-on-main |
1 |
🔴 Tier 1 — Blocking
no-fix-yet (1)
| Issue |
Title |
Fix PRs |
Action |
| #39295 |
C2 & C5: Content turns blank when dragging a slide... |
— |
Investigate: no fix PR cross-referenced from issue |
🟡 Tier 2 — Risk / Review
merged-non-main-only (2)
| Issue |
Title |
Fix PRs |
Action |
| #38618 |
[MAUI] L2 _TabBar Switching Test - Crashes when op... |
#39005 |
Flow fix to main first, then rerun readiness to verify the merged source PR is on main before requesting a backport |
| #38622 |
[MAUI] I1_RTL_FlowDirection - Rotating the iOS sim... |
#38771, #38815 |
Flow fix to main first, then rerun readiness to verify the merged source PR is on main before requesting a backport |
open-on-main (1)
| Issue |
Title |
Fix PRs |
Action |
| #38619 |
[MAUI] J3_Check Window.TitleBar is not reset after... |
#38638, #39274 |
Wait for the main merge before the SR cut; rerun readiness after the release/...-srN branch exists to get the exact backport command. |
Release Readiness — CANDIDATE for next SR (vs release/10.0.1xx-sr11)
Verdict — 🔴 Not Ready
no-fix-yetmerged-non-main-onlyopen-on-mainstale. Re-evaluate after SR cut.Tracker:
net10-sr12· mode=candidate· branch=mainHEAD:
54ab39ea— Improve CI-fix Azure queue failure diagnostics (#39243)Generated: 2026-10-10T14:38:06.1353089Z
Nightly dogfood feed: ✅
dotnet10· ci.inflight — latest10.0.120-ci.inflight.26509.6built today.Expected ship date: Tuesday October 13, 2026 — in 3 days (.NET releases ship on the 2nd Tuesday of each month.)
Regression labels: regressed-in-10.0.110, regressed-in-10.0.120 (mode: explicit)
🔴 Blocking — 1 item(s)
🚩 Candidate PR — SR12 cut point (10.0.120)
The Candidate PR promotes a specific
maincommit as the base for cutting SR12 (10.0.120). The SR branch can't be cut until it merges, so its status gates the whole cycle.No open Candidate PR yet. When ready to cut SR12, open a PR titled
*Candidate*againstmainselecting the target commit — the SR is cut from its merge commit. 1 non-maintainer*Candidate*-titled PR(s) were excluded as not real cut PRs.🧹 Cleanup follow-ups — 2 item(s)
These are housekeeping items that should be addressed but do NOT block this release.
10.0.[120..129]found in version-with-bug dropdown onorigin/main. Top entries: 11.0.0-rc.1, 11.0.0-preview.7, 11.0.0-preview.6.10.0.120) to .github/ISSUE_TEMPLATE/bug-report.yml — can land before or shortly after ship..NET 10 SR13exists. OnceSR12ships, open issues will have nowhere to roll forward to — butSR12can ship first.gh api repos/dotnet/maui/milestones -f title=".NET 10 SR13" -f state=openRecent CI Failure Scanner signals (
ci-scan)Filtered to issues whose
**Branch**: <name>body marker matchesmain(auto-filed by the CI Failure Scanner workflow every 12h). Fresh issues (<24h) are flagged 🆕.No ci-scan issues target
main.📥 Open Fix PRs Inbound — 1 PR(s)
Fix PRs in flight for regression issues. Land these (or their backports) before ship to close out the regression list.
mainShip-readiness checks
origin/mainreports10.0.120— within expected SR12 range [120..129].10.0.[120..129]found in version-with-bug dropdown onorigin/main. Top entries: 11.0.0-rc.1, 11.0.0-preview.7, 11.0.0-preview.6.10.0.120) to .github/ISSUE_TEMPLATE/bug-report.yml — can land before or shortly after ship.main(labelci-scan) — scanner has not flagged recurring CI failures..NET 10 SR13exists. OnceSR12ships, open issues will have nowhere to roll forward to — butSR12can ship first.gh api repos/dotnet/maui/milestones -f title=".NET 10 SR13" -f state=open*Candidate*from a maintainer (OWNER/MEMBER/COLLABORATOR) found onmain(1 non-maintainer PR(s) titled 'Candidate' were excluded as not real cut PRs). The Candidate PR is the mechanism that promotes a specific main commit as the SR cut point.mainselecting the target main commit for the next SR.Release Captain Notes
Add manual notes here. Anything between these begin/end markers is preserved across automated re-runs.
CI Status — overall:
stalestalestalestaleWhat's New in SR — 65 commits
sr-source-prs.txt)Reverts
87f811b87220e42f3d7ff41cRegression Candidates — 4 issues scanned
Summary
merged-non-main-onlyno-fix-yetopen-on-main🔴 Tier 1 — Blocking
no-fix-yet(1)🟡 Tier 2 — Risk / Review
merged-non-main-only(2)open-on-main(1)