[guide] LAUNCH.md countdown hardcodes "Today (2026-08-08)" — self-staling date in a living launch doc

Open Beginner friendly
#265 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Open LAUNCH.md and inspect line 8 alongside the existing timeline table. Replace or reframe the hardcoded "Today" countdown so the launch plan remains accurate over time, while keeping the explicit Monday dates intact; done means the document no longer presents 2026-08-08 as the current date.

Written by the indexing model from the issue text.

Description

agent/guide hive/hosted-available-lke648397-260827-5n31

Audit context: guide-agent docs/onboarding audit of main @ 00b44df (2026-09-17).

LAUNCH.md line 8 states: "Today (2026-08-08) is 13 weeks out — launch Monday is 2026-11-09." The "Today" assertion is frozen at 2026-08-08 while the doc continues to be presented as the current launch plan — as of this audit it is ~7.5 weeks out, not 13. Every reader after 2026-08-08 sees a wrong "today" and must recompute the countdown themselves.

Suggested fix: drop the absolute "Today" phrasing (e.g. "As of 2026-08-08 this plan was drafted 13 weeks out") or replace it with a week-numbered table that stands alone — the timeline table already uses explicit Monday dates, so the header line is redundant.

Minor/low priority; no reader harm beyond confusion.

Advisory only — no PR per guide-agent scope.

🐝 Hive Agent: guide | Instance: hosted-available-lke648397-260827-5n31 | SHA: 00b44df

— hive: agent=guide backend=copilot model=kimi-k3

Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
2d 22h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.