Skip to content

armgit / Pulse

Public Imported from GitHub
0

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.

Align triage disclosure with current release and retest policy

pulse-triage[bot]f7cd68379b00
diff --git a/docs/AI_TRANSPARENCY.md b/docs/AI_TRANSPARENCY.md
index 4533950c2b..307fd0b4d5 100644
--- a/docs/AI_TRANSPARENCY.md
+++ b/docs/AI_TRANSPARENCY.md
@@ -57,11 +57,18 @@ requests are opened by `pulse-triage[bot]` and state what changed, why it
was needed, which reports or demand-ledger entries it answers, and what
validation was used, so the record on GitHub is the record of the decision.
-Every 14 days after the last stable release, the train cuts the next minor
-release candidate from the head of `main`. It carries everything on `main` at
-that cut, not a selected set of fixes. Repairs go on `main`, not onto an older
-release line. An early cut can bring the next minor release forward when an
-important fix should not wait. Patch releases are not scheduled.
+Stable publication is targeted seven days after the last stable release. The
+next minor release candidate becomes eligible one day earlier, reserving its
+full 24-hour soak; preparation and qualification can move publication later.
+It is cut from the head of `main` and carries everything on `main` at that cut,
+not a selected set of fixes. Repairs go on `main`, not onto an older release
+line. Patch releases are not scheduled.
+
+Between stable releases, daily betas carry new changes from `main`; no beta is
+cut within a day of the candidate being due. An important fix ships in the next
+beta, not through an early candidate or stable release. Work merged during a
+candidate's soak waits for the next cycle unless a `release-blocker` requires
+a fresh candidate. A beta is not promoted to stable.
The candidate soaks for 24 hours on the opt-in preview channel, then is promoted
unchanged to stable unless an open issue labelled `release-blocker` stops
@@ -90,9 +97,12 @@ explanation; a feature request's demand-ledger entry is not an implemented featu
After a fix for every reported symptom ships in a stable release, the maintainer
names that version and asks for a retest in the original issue. That reply says
the issue will be closed after 14 days without a reply and can be reopened.
-The 14 days start with that stable-release retest reply, not the fix commit,
-a beta or a release candidate. Only retest when it is safe; do not repeat an
-outage, update or backup just to answer.
+Normally, the 14 days start with that stable-release retest reply. If an earlier
+retest request named a beta or release candidate carrying the same fix, and the
+limit on repeated unanswered contact prevents another reply, count from the
+later of that request and the stable release's publication. A beta or release
+candidate alone never starts the timeout, nor does a fix commit. Only retest
+when it is safe; do not repeat an outage, update or backup just to answer.
Only after at least 14 days without any reply from the reporter, and with no
other person reporting the same problem since that retest request, may the
diff --git a/docs/RELEASE_PROCESS.md b/docs/RELEASE_PROCESS.md
index 1cdd06fbc3..54b4aa516b 100644
--- a/docs/RELEASE_PROCESS.md
+++ b/docs/RELEASE_PROCESS.md
@@ -68,10 +68,9 @@ Releases follow a fixed schedule rather than individual judgment.
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 one
- that starts its own soak. A candidate carries everything merged to `main` at the
- cut. Nothing is selected for it or added to it afterwards.
+ Nothing brings that cut forward: an important fix ships in the next daily
+ beta. A candidate carries everything merged to `main` at the cut. Nothing is
+ selected for it or added to it afterwards.
2. **Qualify and publish it.** Required checks include targeted tests, installation
smoke checks, release-pipeline validation, and recorded rollback instructions.
RCs also run the integration checks required for stable releases. Release notes
@@ -95,9 +94,11 @@ Releases follow a fixed schedule rather than individual judgment.
- A defect that the current stable release already has is fixed on `main` and ships
in the next release.
-An important fix can bring the next candidate cut forward. It still carries
-everything on `main` at the cut and goes through the same required checks and
-24-hour soak; it is not a selected patch release or a testing exemption.
+Work merged during a candidate's soak waits for the next cycle's betas and
+candidate. Only a `release-blocker` requires a fresh candidate; an important fix
+alone does not replace a soaking candidate or bring stable publication forward.
+Every replacement still carries everything on `main` at its cut and goes
+through the same required checks and full 24-hour soak.
## Taking part in Preview testing
diff --git a/frontend-modern/public/docs/AI_TRANSPARENCY.md b/frontend-modern/public/docs/AI_TRANSPARENCY.md
index 4533950c2b..307fd0b4d5 100644
--- a/frontend-modern/public/docs/AI_TRANSPARENCY.md
+++ b/frontend-modern/public/docs/AI_TRANSPARENCY.md
@@ -57,11 +57,18 @@ requests are opened by `pulse-triage[bot]` and state what changed, why it
was needed, which reports or demand-ledger entries it answers, and what
validation was used, so the record on GitHub is the record of the decision.
-Every 14 days after the last stable release, the train cuts the next minor
-release candidate from the head of `main`. It carries everything on `main` at
-that cut, not a selected set of fixes. Repairs go on `main`, not onto an older
-release line. An early cut can bring the next minor release forward when an
-important fix should not wait. Patch releases are not scheduled.
+Stable publication is targeted seven days after the last stable release. The
+next minor release candidate becomes eligible one day earlier, reserving its
+full 24-hour soak; preparation and qualification can move publication later.
+It is cut from the head of `main` and carries everything on `main` at that cut,
+not a selected set of fixes. Repairs go on `main`, not onto an older release
+line. Patch releases are not scheduled.
+
+Between stable releases, daily betas carry new changes from `main`; no beta is
+cut within a day of the candidate being due. An important fix ships in the next
+beta, not through an early candidate or stable release. Work merged during a
+candidate's soak waits for the next cycle unless a `release-blocker` requires
+a fresh candidate. A beta is not promoted to stable.
The candidate soaks for 24 hours on the opt-in preview channel, then is promoted
unchanged to stable unless an open issue labelled `release-blocker` stops
@@ -90,9 +97,12 @@ explanation; a feature request's demand-ledger entry is not an implemented featu
After a fix for every reported symptom ships in a stable release, the maintainer
names that version and asks for a retest in the original issue. That reply says
the issue will be closed after 14 days without a reply and can be reopened.
-The 14 days start with that stable-release retest reply, not the fix commit,
-a beta or a release candidate. Only retest when it is safe; do not repeat an
-outage, update or backup just to answer.
+Normally, the 14 days start with that stable-release retest reply. If an earlier
+retest request named a beta or release candidate carrying the same fix, and the
+limit on repeated unanswered contact prevents another reply, count from the
+later of that request and the stable release's publication. A beta or release
+candidate alone never starts the timeout, nor does a fix commit. Only retest
+when it is safe; do not repeat an outage, update or backup just to answer.
Only after at least 14 days without any reply from the reporter, and with no
other person reporting the same problem since that retest request, may the
diff --git a/frontend-modern/public/docs/RELEASE_PROCESS.md b/frontend-modern/public/docs/RELEASE_PROCESS.md
index 1cdd06fbc3..54b4aa516b 100644
--- a/frontend-modern/public/docs/RELEASE_PROCESS.md
+++ b/frontend-modern/public/docs/RELEASE_PROCESS.md
@@ -68,10 +68,9 @@ Releases follow a fixed schedule rather than individual judgment.
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 one
- that starts its own soak. A candidate carries everything merged to `main` at the
- cut. Nothing is selected for it or added to it afterwards.
+ Nothing brings that cut forward: an important fix ships in the next daily
+ beta. A candidate carries everything merged to `main` at the cut. Nothing is
+ selected for it or added to it afterwards.
2. **Qualify and publish it.** Required checks include targeted tests, installation
smoke checks, release-pipeline validation, and recorded rollback instructions.
RCs also run the integration checks required for stable releases. Release notes
@@ -95,9 +94,11 @@ Releases follow a fixed schedule rather than individual judgment.
- A defect that the current stable release already has is fixed on `main` and ships
in the next release.
-An important fix can bring the next candidate cut forward. It still carries
-everything on `main` at the cut and goes through the same required checks and
-24-hour soak; it is not a selected patch release or a testing exemption.
+Work merged during a candidate's soak waits for the next cycle's betas and
+candidate. Only a `release-blocker` requires a fresh candidate; an important fix
+alone does not replace a soaking candidate or bring stable publication forward.
+Every replacement still carries everything on `main` at its cut and goes
+through the same required checks and full 24-hour soak.
## Taking part in Preview testing
diff --git a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
index 009ae4d352..4ec73c0764 100644
--- a/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
+++ b/frontend-modern/src/features/docs/__tests__/issueFollowThroughGuide.test.ts
@@ -35,7 +35,12 @@ describe('public issue follow-through guidance', () => {
expect(paragraphs).toHaveLength(4);
expect(prose(paragraphs[0])).toContain('no reported symptom left unresolved');
expect(prose(paragraphs[1])).toContain('start with that stable-release retest reply');
- expect(prose(paragraphs[1])).toContain('not the fix commit, a beta or a release candidate');
+ expect(prose(paragraphs[1])).toContain('carrying the same fix');
+ expect(prose(paragraphs[1])).toContain('limit on repeated unanswered contact prevents another reply');
+ expect(prose(paragraphs[1])).toContain("later of that request and the stable release's publication");
+ expect(prose(paragraphs[1])).toContain(
+ 'A beta or release candidate alone never starts the timeout, nor does a fix commit',
+ );
const emphasis = paragraphs[2].querySelector('strong');
expect(emphasis).not.toBeNull();
expect(prose(emphasis!)).toBe('not confirmed resolution');
@@ -69,4 +74,23 @@ describe('public issue follow-through guidance', () => {
expect(article.querySelector('#how-changes-land-and-ship')).not.toBeNull();
expect(article.querySelector('#authority-and-responsibility')).not.toBeNull();
});
+
+ it('keeps the disclosure and its linked release guide on the weekly, no-early-cut policy', () => {
+ const article = renderGuide('AI_TRANSPARENCY', source);
+ const text = prose(article);
+ expect(text).toContain('Stable publication is targeted seven days after the last stable release');
+ expect(text).toContain('one day earlier, reserving its full 24-hour soak');
+ expect(text).toContain('An important fix ships in the next beta, not through an early candidate or stable release');
+ expect(text).toContain('unless a release-blocker requires a fresh candidate');
+ expect(text).not.toContain('Every 14 days');
+ expect(text).not.toContain('An early cut can bring');
+ expect(article.querySelector('a[href="/docs/RELEASE_PROCESS"]')?.hasAttribute('data-doc-link')).toBe(true);
+ const releaseSource = readFileSync(path.join(shippedDocs, 'RELEASE_PROCESS.md'), 'utf8');
+ expect(releaseSource).toBe(readFileSync(path.join(repoRoot, 'docs/RELEASE_PROCESS.md'), 'utf8'));
+ const release = renderGuide('RELEASE_PROCESS', releaseSource);
+ expect(prose(release)).toContain('Nothing brings that cut forward');
+ expect(prose(release)).toContain('an important fix ships in the next daily beta');
+ expect(prose(release)).toContain('Only a release-blocker requires a fresh candidate');
+ expect(prose(release)).not.toContain('can bring');
+ });
});
diff --git a/scripts/tests/test_transparency_docs.py b/scripts/tests/test_transparency_docs.py
index ac311cddfd..4283634c54 100644
--- a/scripts/tests/test_transparency_docs.py
+++ b/scripts/tests/test_transparency_docs.py
@@ -23,13 +23,33 @@ class TransparencyDocsTest(unittest.TestCase):
def test_all_main_minor_cycle_not_selective_backports(self):
for path, text in self.documents():
with self.subTest(document=path):
- self.assertIn("Every 14 days after the last stable release", text)
- self.assertIn("next minor release candidate from the head of `main`", text)
+ self.assertIn("Stable publication is targeted seven days after the last stable release", text)
+ self.assertIn("next minor release candidate becomes eligible one day earlier", text)
+ self.assertIn("reserving its full 24-hour soak", text)
+ self.assertIn("preparation and qualification can move publication later", text)
+ self.assertIn("cut from the head of `main`", text)
self.assertIn("everything on `main` at that cut", text)
self.assertIn("Repairs go on `main`, not onto an older release line", text)
- self.assertIn("An early cut can bring the next minor release forward", text)
+ self.assertIn("An important fix ships in the next beta, not through an early candidate or stable release", text)
+ self.assertIn("no beta is cut within a day of the candidate being due", text)
self.assertIn("Patch releases are not scheduled", text)
self.assertNotIn("takes only backports", text)
+ self.assertNotIn("Every 14 days", text)
+ self.assertNotIn("An early cut can bring", text)
+
+ def test_linked_release_guide_does_not_offer_an_early_cut_or_soak_replacement(self):
+ for directory in ("docs", "frontend-modern/public/docs"):
+ path = ROOT / directory / "RELEASE_PROCESS.md"
+ text = " ".join(path.read_text(encoding="utf-8").split()).replace("**", "")
+ with self.subTest(document=path):
+ self.assertIn("seven days after the last stable release", text)
+ self.assertIn("one day earlier", text)
+ self.assertIn("Nothing brings that cut forward", text)
+ self.assertIn("an important fix ships in the next daily beta", text)
+ self.assertIn("Only a `release-blocker` requires a fresh candidate", text)
+ self.assertIn("does not replace a soaking candidate or bring stable publication forward", text)
+ self.assertIn("same required checks and full 24-hour soak", text)
+ self.assertNotIn("can bring", text)
def test_blockers_need_a_fresh_candidate_not_a_changed_soak(self):
for path, text in self.documents():
@@ -75,7 +95,10 @@ class TransparencyDocsTest(unittest.TestCase):
self.assertIn("fix for every reported symptom ships in a stable release", text)
self.assertIn("closed after 14 days without a reply and can be reopened", text)
self.assertIn("start with that stable-release retest reply", text)
- self.assertIn("not the fix commit, a beta or a release candidate", text)
+ self.assertIn("earlier retest request named a beta or release candidate carrying the same fix", text)
+ self.assertIn("limit on repeated unanswered contact prevents another reply", text)
+ self.assertIn("later of that request and the stable release's publication", text)
+ self.assertIn("A beta or release candidate alone never starts the timeout, nor does a fix commit", text)
self.assertIn("at least 14 days without any reply from the reporter", text)
self.assertIn("no other person reporting the same problem since that retest request", text)