From fc21480134db631316edb72f779bb3e9e358137d Mon Sep 17 00:00:00 2001 From: Rafael Vuijk Date: Wed, 30 Sep 2026 11:38:40 +0000 Subject: [PATCH 1/3] A parent is never due before its children The two rules Happypig375 set on #718: a parent issue's milestone is never earlier than any child's, in the order the versions run and then Future and Guiding principles, so a child moved later takes its parent with it; and "under" is GitHub's sub-issue relationship, set in the turn an issue is filed, before any comment says it. With the command that sets the link, which takes the child's id rather than its number. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura --- AGENTS.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 757f7ee95..288556c16 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -734,6 +734,16 @@ triaged, every issue is on one, and the milestone says what kind of change it is A Goal with no last piece to aim at is on Guiding principles ([#1511](https://github.com/asc-community/AngouriMath/pull/1511#issuecomment-5858231058)). - A proposal without `Accepted` is on Future until it is decided: a version would decide it. +- **A parent is never due before its children.** Milestones run through the versions in order, + then Future, then Guiding principles, and a parent issue's is never earlier than any child's: + when a child moves later than its parent, the parent moves with it + ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910345918)). So + #233 went from `2.6.0` to `2.8` when its children #1469 and #1486 were on `2.8`, and #718, a + parent with no milestone, went to Future. And "under" is GitHub's sub-issue relationship, not + prose: an issue that belongs under another is linked in the turn it is filed, and a comment says + "under" only once the link is there + ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910315961)) -- + the tree is what the backlog is read by, and a word in a comment is invisible to it. An issue you open has its type and its milestone from the moment it is filed, which the reply that triages someone else's issue does for theirs. `gh issue create --milestone` sets the one; @@ -743,6 +753,13 @@ the type needs a second call, since `gh issue create` has no flag for it: gh api -X PATCH repos/asc-community/AngouriMath/issues/ -f type=Bug # Bug, Feature, Maintenance or Goal ``` +and a sub-issue link takes the child's id rather than its number: + +``` +gh api -X POST repos/asc-community/AngouriMath/issues//sub_issues \ + -F sub_issue_id=$(gh api repos/asc-community/AngouriMath/issues/ --jq .id) +``` + When a PR merges, check its issue's milestone still describes where the change lands — a fix that turned out breaking moves to the major, with a `BREAKING-CHANGES.md` entry. Release clearance is the milestone read through: every open item on it either ships in this release or is From ff8e41668694de3ba4433a6c444b6c49a24351d5 Mon Sep 17 00:00:00 2001 From: Rafael Vuijk Date: Wed, 30 Sep 2026 12:11:56 +0000 Subject: [PATCH 2/3] Children taken up now pull their parent forward Happypig375's answer on #718 an hour later: the in-progress children move to the next minor and take their parent with them, and #718 is on Guiding principles. The example of #233 going to 2.8 described a state that no longer holds, so the paragraph says the rule both ways instead. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura --- AGENTS.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 288556c16..6efcb7746 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -737,11 +737,13 @@ triaged, every issue is on one, and the milestone says what kind of change it is - **A parent is never due before its children.** Milestones run through the versions in order, then Future, then Guiding principles, and a parent issue's is never earlier than any child's: when a child moves later than its parent, the parent moves with it - ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910345918)). So - #233 went from `2.6.0` to `2.8` when its children #1469 and #1486 were on `2.8`, and #718, a - parent with no milestone, went to Future. And "under" is GitHub's sub-issue relationship, not - prose: an issue that belongs under another is linked in the turn it is filed, and a comment says - "under" only once the link is there + ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910345918)). The + other way round, children being worked on now are on the next minor, and they pull their parent + forward with them rather than leaving it where the plan once was + ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910745181)); a + parent with no last piece to aim at, #718 itself, is on Guiding principles. And "under" is + GitHub's sub-issue relationship, not prose: an issue that belongs under another is linked in the + turn it is filed, and a comment says "under" only once the link is there ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910315961)) -- the tree is what the backlog is read by, and a word in a comment is invisible to it. From d6c10b66836b912ba3bd19eab512a7f3b0f50ed9 Mon Sep 17 00:00:00 2001 From: Rafael Vuijk Date: Wed, 30 Sep 2026 12:39:55 +0000 Subject: [PATCH 3/3] The parent rule runs one way; bringing work earlier is scheduling Happypig375 on #1626: "It's really just scheduling. We need calculus to be completed earlier because it's the door to university level mathematics and beyond." The previous revision read his move of the integration work to 2.6 as a second direction of the rule. It is not: a child delayed beyond its parent moves the parent, and bringing work earlier is a decision with its own reason, which the paragraph now gives as his. Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura --- AGENTS.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 6efcb7746..046a98a03 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -738,10 +738,11 @@ triaged, every issue is on one, and the milestone says what kind of change it is then Future, then Guiding principles, and a parent issue's is never earlier than any child's: when a child moves later than its parent, the parent moves with it ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910345918)). The - other way round, children being worked on now are on the next minor, and they pull their parent - forward with them rather than leaving it where the plan once was - ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910745181)); a - parent with no last piece to aim at, #718 itself, is on Guiding principles. And "under" is + rule runs one way. Bringing work *earlier* is a scheduling decision, not a consequence of it: + the integration work under #233 goes to `2.6.0` because calculus comes first, being the + door to university mathematics and beyond + ([#1626](https://github.com/asc-community/AngouriMath/pull/1626#issuecomment-5911144638)), and + #718, a parent with no last piece to aim at, is on Guiding principles. And "under" is GitHub's sub-issue relationship, not prose: an issue that belongs under another is linked in the turn it is filed, and a comment says "under" only once the link is there ([#718](https://github.com/asc-community/AngouriMath/issues/718#issuecomment-5910315961)) --