Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Record the daily beta release cadence
rcourtman316f4d51462d
diff --git a/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md b/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.mdindex f2b926293a..dc9bfbb151 100644--- a/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md+++ b/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md@@ -244,6 +244,15 @@ release steward, its publisher, the nightly rehearsal and the release-linelane. Every other document that describes releases defers to this section andto that direction.+0. **Betas.** From the last stable release until the candidate is due, the+ train cuts a beta for the next minor from the head of `main` every 24 hours+ when there are new changes. This follows the founder's direction on+ 13 October 2026 to publish almost daily betas. Published betas remain at+ least 24 hours apart, and no beta is cut within a day of the candidate being+ due. Already recorded publication and retry deadlines are honoured when+ the cadence changes. Betas use the normal prerelease qualification and+ publication path, do not soak or promote, and a failed beta does not hold+ the candidate or stable release.1. **Cut.** Fourteen days after the last stable release, or earlier on`pulse-maintainer-ship request`, the train cuts a release candidate for thenext minor version from the head of `main`. A release carries everything ondiff --git a/docs/release-control/v6/internal/status.json b/docs/release-control/v6/internal/status.jsonindex ad506c1785..36f3fce00c 100644--- a/docs/release-control/v6/internal/status.json+++ b/docs/release-control/v6/internal/status.json@@ -11282,6 +11282,18 @@"lane_ids": ["L1"]+ },+ {+ "id": "daily-beta-release-cadence",+ "summary": "Founder direction on 2026-10-13: publish almost daily betas. The release train cuts the next minor beta from main every 24 hours when there are new changes, honours already recorded publication and retry deadlines, skips empty cuts and the final day before the release candidate is due, and retains prerelease qualification and at least 24 hours between published betas. Beta failures do not hold the release candidate or stable release. The 14-day candidate cadence, exact-candidate stable promotion and clean 24-hour RC soak remain unchanged. RELEASE_PROMOTION_POLICY.md, Release Train, is the in-repository statement; the infrastructure repository owns the executable schedule.",+ "kind": "release-policy",+ "decided_at": "2026-10-13",+ "subsystem_ids": [+ "deployment-installability"+ ],+ "lane_ids": [+ "L1"+ ]}]}