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
Correct release help to the weekly stable target
pulse-triage[bot]98ca169e12b9
diff --git a/docs/RELEASE_PROCESS.md b/docs/RELEASE_PROCESS.mdindex d8ad3971bb..1cdd06fbc3 100644--- a/docs/RELEASE_PROCESS.md+++ b/docs/RELEASE_PROCESS.md@@ -64,10 +64,12 @@ with a chart asset. Follow the existing installation'sReleases follow a fixed schedule rather than individual judgment.-1. **Cut a candidate from `main`.** Fourteen days after the last stable release,- the next release candidate is cut from `main`, provided `main` has changed since- that release. An important fix that should not wait for the schedule can bring- that cut forward, or replace a candidate that is still soaking with a fresh one+1. **Cut a candidate from `main`.** Stable publication is targeted **seven days+ after the last stable release**, provided `main` has changed since that release.+ The next release candidate becomes eligible **one day earlier**, reserving the+ full 24-hour soak. Preparation and qualification can move publication later.+ An important fix that should not wait for the schedule can bring that cut+ forward, or replace a candidate that is still soaking with a fresh onethat starts its own soak. A candidate carries everything merged to `main` at thecut. Nothing is selected for it or added to it afterwards.2. **Qualify and publish it.** Required checks include targeted tests, installationdiff --git a/frontend-modern/browser-tests/release-channel-help.cjs b/frontend-modern/browser-tests/release-channel-help.cjsindex 899bcfaea5..087a8d8ec3 100644--- a/frontend-modern/browser-tests/release-channel-help.cjs+++ b/frontend-modern/browser-tests/release-channel-help.cjs@@ -97,12 +97,17 @@ const result = { result: 'incomplete', source_sha: binding.source_sha,'No beta is cut within a day', 'no soak and is never promoted to stable','A fix merged after a beta was cut is not in that beta','only when a stable release containing it ships', 'not a selected patch release or a testing exemption',- 'Fourteen days after the last stable release', 'Do not repeat a guest freeze',+ 'seven days after the last stable release', 'one day earlier',+ 'reserving the full 24-hour soak', 'Preparation and qualification can move publication later',+ 'Do not repeat a guest freeze','if the problem persists, reply on the original issue']) assert(text.includes(phrase), phrase);assert(!text.includes('urgent hotfix exception'));- record.checks.push('shipped update-guide entry; daily-beta scope, cut/inclusion, stable separation, unchanged candidate checks and safe retest');+ assert(!text.includes('Fourteen days after the last stable release'));+ record.checks.push('shipped update-guide entry; daily-beta scope, cut/inclusion, stable separation, weekly stable target, early eligibility, unchanged candidate checks and safe retest');await page.goto(`${origin}/docs/RELEASE_PROCESS#daily-betas`, { waitUntil: 'domcontentloaded' });await atFragment('daily-betas'); await capture('betas');+ await page.goto(`${origin}/docs/RELEASE_PROCESS#how-releases-are-prepared`, { waitUntil: 'domcontentloaded' });+ await atFragment('how-releases-are-prepared'); await capture('preparation');await page.goto(`${origin}/docs/RELEASE_PROCESS#cadence-and-stable-promotion`, { waitUntil: 'domcontentloaded' });await atFragment('cadence-and-stable-promotion'); await capture('promotion');await page.goto(`${origin}/docs/RELEASE_PROCESS#taking-part-in-preview-testing`, { waitUntil: 'domcontentloaded' });diff --git a/frontend-modern/public/docs/RELEASE_PROCESS.md b/frontend-modern/public/docs/RELEASE_PROCESS.mdindex d8ad3971bb..1cdd06fbc3 100644--- a/frontend-modern/public/docs/RELEASE_PROCESS.md+++ b/frontend-modern/public/docs/RELEASE_PROCESS.md@@ -64,10 +64,12 @@ with a chart asset. Follow the existing installation'sReleases follow a fixed schedule rather than individual judgment.-1. **Cut a candidate from `main`.** Fourteen days after the last stable release,- the next release candidate is cut from `main`, provided `main` has changed since- that release. An important fix that should not wait for the schedule can bring- that cut forward, or replace a candidate that is still soaking with a fresh one+1. **Cut a candidate from `main`.** Stable publication is targeted **seven days+ after the last stable release**, provided `main` has changed since that release.+ The next release candidate becomes eligible **one day earlier**, reserving the+ full 24-hour soak. Preparation and qualification can move publication later.+ An important fix that should not wait for the schedule can bring that cut+ forward, or replace a candidate that is still soaking with a fresh onethat starts its own soak. A candidate carries everything merged to `main` at thecut. Nothing is selected for it or added to it afterwards.2. **Qualify and publish it.** Required checks include targeted tests, installation