Indicate rebootstrap requirements in source-build release announcements

[mthalman]

Source-build release announcements do not clearly state whether consumers can build using the previous source-built release or must rebootstrap.

Proposal

Add a field to every source-build release announcement

Rebootstrap required: Yes/No

[github-actions]

🏷️ Source-build triage pass — 2026-08-13 16:20 UTC

📋 Classification

Field	Value
Area	area-release
Additional area(s)	area-doc
Kind	process
Severity	S4 — documentation/process improvement to release announcements; no broken scenario
Affected version(s)	current
Repro	n/a — process improvement request, not a bug

🚦 Priority

• Blocking: not blocking
• Urgency: ⚪ backlog — no milestone

  Low-friction process improvement; no release is blocked and the information can be added opportunistically.

👥 Routing

• Team: @dotnet/source-build
• Possible SME(s): mthalman, MichaelSimons
  • mthalman — issue author; active on release process and documentation issues (e.g., filed Feature band release PRs timing issue #5636, boostrap-new-os.md doc is outdated or obsolete #4729)
  • MichaelSimons — filed closely related Document expectations around when rebootstrapping is needed for pre-releases #5229 ("Document expectations around when rebootstrapping is needed for pre-releases")

🔗 Cross-references

• Recommended labels: add area-release, add area-doc
• Related issues: Document expectations around when rebootstrapping is needed for pre-releases #5229 (overlapping goal: documenting rebootstrap requirements for pre-releases)
• Possible duplicate of: none (complements Document expectations around when rebootstrapping is needed for pre-releases #5229 but scoped to release announcements specifically)

✅ Assessment

• Confidence: high
• Needs human?: no

---

Restricted mode — no labels or milestone applied. A maintainer should manually apply any accepted labels and milestone.

Generated by Triage · 67.4 AIC · ⌖ 11.1 AIC · ⊞ 24.6K · ◷