Records the sync of MIL-003 to Gitea and one fix that it made necessary. Documents only; no code changes.
The MIL-003 Milestone (id 74) and its issues #22 to #27 are created on Gitea. Creating them exposed a collision: task 6 of MIL-003 had the same title as task 6 of MIL-001, and sync-project.sh matches issues by title across all milestones, so it overwrote the closed MIL-001 issue #6 (it moved it into the MIL-003 Milestone and added a Phase: MIL-003 line to its body).
What was done about it
Issue #6 was restored: original text, the MIL-001 Milestone, a Phase: MIL-001 line, still closed. All 27 issues and pull requests were counted by Milestone and state afterwards; nothing else moved.
MIL-003 task 6 is renamed to "Review the visible-colours code against qc-programming-python", which is issue #27, created by hand. No other task title is shared between the milestone documents, so a later re-sync cannot clobber an issue.
What changes in the repository
MIL-003: task 6 renamed; new Version History row, accepted by S01 in chat.
RC-008: a delta confirmation for the rename. No criterion result changes: the summary, deliverable, criteria, traceability, ownership and date are untouched. New row, accepted by S01.
Project Plan: the MIL-003 gateway links to its Milestone. That is a link update, so there is no new Version History row.
The commit links in the two new rows are resolved in the last commit.
Worth proposing upstream to the framework: the sync should match titles within one milestone, or warn on duplicates across milestones. This repository does not edit the framework.
After this merges
The plan-first gate is open for the six MIL-003 tasks (Task: MIL-003#1 to #6); the code follows on its own branch.
Issues
No issue closed: this records the sync and a rename. Issues #22 to #27 stay open for the code.
## Summary
Records the sync of MIL-003 to Gitea and one fix that it made necessary. Documents only; no code changes.
The MIL-003 Milestone (id 74) and its issues #22 to #27 are created on Gitea. Creating them exposed a collision: task 6 of MIL-003 had the same title as task 6 of MIL-001, and `sync-project.sh` matches issues by title across all milestones, so it overwrote the closed MIL-001 issue #6 (it moved it into the MIL-003 Milestone and added a `Phase: MIL-003` line to its body).
**What was done about it**
- Issue #6 was restored: original text, the MIL-001 Milestone, a `Phase: MIL-001` line, still closed. All 27 issues and pull requests were counted by Milestone and state afterwards; nothing else moved.
- MIL-003 task 6 is renamed to "Review the visible-colours code against qc-programming-python", which is issue #27, created by hand. No other task title is shared between the milestone documents, so a later re-sync cannot clobber an issue.
**What changes in the repository**
- MIL-003: task 6 renamed; new Version History row, accepted by S01 in chat.
- RC-008: a delta confirmation for the rename. No criterion result changes: the summary, deliverable, criteria, traceability, ownership and date are untouched. New row, accepted by S01.
- Project Plan: the MIL-003 gateway links to its Milestone. That is a link update, so there is no new Version History row.
- The commit links in the two new rows are resolved in the last commit.
Worth proposing upstream to the framework: the sync should match titles within one milestone, or warn on duplicates across milestones. This repository does not edit the framework.
## After this merges
The plan-first gate is open for the six MIL-003 tasks (`Task: MIL-003#1` to `#6`); the code follows on its own branch.
## Issues
No issue closed: this records the sync and a rename. Issues #22 to #27 stay open for the code.
The MIL-003 milestone (id 74) and its issues #22 to #27 are created on Gitea.
Creating them exposed a collision: task 6 of MIL-003 had the same title as
task 6 of MIL-001, and sync-project.sh matches issues by title, so it
overwrote the closed MIL-001 issue #6 (milestone and a Phase line). Issue #6
was restored, and MIL-003 task 6 is renamed "Review the visible-colours code
against qc-programming-python", which is issue #27. No other task title is
shared between the milestone documents.
- MIL-003: rename task 6 (new Version History row, accepted by S01).
- RC-008: add the delta confirmation for the rename; no criterion result
changes (new row, accepted by S01).
- PP-001: link the MIL-003 gateway to its Milestone (a link update, no new
Version History row).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Records the sync of MIL-003 to Gitea and one fix that it made necessary. Documents only; no code changes.
The MIL-003 Milestone (id 74) and its issues #22 to #27 are created on Gitea. Creating them exposed a collision: task 6 of MIL-003 had the same title as task 6 of MIL-001, and
sync-project.shmatches issues by title across all milestones, so it overwrote the closed MIL-001 issue #6 (it moved it into the MIL-003 Milestone and added aPhase: MIL-003line to its body).What was done about it
Phase: MIL-001line, still closed. All 27 issues and pull requests were counted by Milestone and state afterwards; nothing else moved.What changes in the repository
Worth proposing upstream to the framework: the sync should match titles within one milestone, or warn on duplicates across milestones. This repository does not edit the framework.
After this merges
The plan-first gate is open for the six MIL-003 tasks (
Task: MIL-003#1to#6); the code follows on its own branch.Issues
No issue closed: this records the sync and a rename. Issues #22 to #27 stay open for the code.