From 1282bc03b323a2237297c4a1c9d1c43f318117b5 Mon Sep 17 00:00:00 2001 From: Jeffrey Phillips Freeman Date: Tue, 24 Feb 2026 17:17:58 -0500 Subject: [PATCH] Docs: Updated timeline --- CONTRIBUTING.md | 16 +-- docs/timeline.md | 251 ++++++++++++++++++++++++++--------------------- 2 files changed, 148 insertions(+), 119 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f96d62fd..f3e7fe67 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -615,13 +615,15 @@ Every issue must include: during triaging. Do **not** assign `MoSCoW/` labels — these are set exclusively by the project owner. -- **Milestone:** Every issue that has moved beyond `State/Unverified` must be assigned to a - milestone. Issues in `State/Unverified` may optionally have a milestone — it is not required - at creation time, but is typically assigned by a maintainer during triaging when the issue is - moved to `State/Verified`. Once an issue is in any active state (`State/Verified`, - `State/In Progress`, `State/Paused`, `State/In Review`, or `State/Completed`), a milestone - is mandatory. If no appropriate milestone exists, discuss with the project owner before - proceeding. +- **Milestone:** Every non-Epic, non-Legendary issue that has moved beyond `State/Unverified` + must be assigned to a milestone. `Type/Epic` and `Type/Legendary` issues are exempt from + this requirement because they typically span multiple milestones; a milestone may optionally + be assigned to them but is not required. Issues in `State/Unverified` may optionally have a + milestone — it is not required at creation time, but is typically assigned by a maintainer + during triaging when the issue is moved to `State/Verified`. Once a non-Epic, non-Legendary + issue is in any active state (`State/Verified`, `State/In Progress`, `State/Paused`, + `State/In Review`, or `State/Completed`), a milestone is mandatory. If no appropriate + milestone exists, discuss with the project owner before proceeding. - **Branch/Tag (Ref):** Forgejo issues have a **branch/tag** field (the `Ref` field on the issue form) that associates the issue with a specific branch or tag in the repository. The rules for this field depend on the nature of the issue: diff --git a/docs/timeline.md b/docs/timeline.md index 497f8524..03a9cadd 100644 --- a/docs/timeline.md +++ b/docs/timeline.md @@ -17,7 +17,7 @@ saturday are closed sunday are closed printscale weekly zoom 2 -today is 2026-02-23 +today is 2026-02-24 today is colored in #FF6666