From 6693574f7e6b157901ec0f831cdb0aac46274f4d Mon Sep 17 00:00:00 2001 From: Vijit Singh Date: Thu, 18 Jun 2026 12:22:44 -0500 Subject: [PATCH] content: fix stale roadmap comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The roadmap comment said it was based on "the v1.1 / v2 milestones; rigforge v1.0 is fully closed", but the rendered roadmap below it now spans v1.1–v1.6 + v2 and both repos have forward milestones. Reword to match (Pithead drives the version themes, RigForge ships in lockstep). Non-rendered comment only — no copy, roadmap, or version-badge change. Co-Authored-By: Claude Opus 4.8 (1M context) --- data/content.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/data/content.yaml b/data/content.yaml index faea64f..28f1ca5 100644 --- a/data/content.yaml +++ b/data/content.yaml @@ -187,8 +187,9 @@ projects: href: "https://github.com/p2pool-starter-stack/rigforge/blob/main/docs/benchmarks.md", } -# High-level roadmap, sequenced from the repos' milestones & open issues (pithead #167 v1.0 waves + -# the v1.1 / v2 milestones; rigforge v1.0 is fully closed). No dates — waves and versions only. +# High-level roadmap, sequenced from both repos' milestones. Pithead drives the version themes +# (v1.1 privacy through v1.6 deploy-anywhere, then v2 appliance); RigForge ships in lockstep. No +# dates; waves and versions only. roadmap: eyebrow: "// the roadmap" title: "v1.0 is live. Now, the road to the appliance era."