NodetteHQ/PureXML
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Rebuild roadmap issue tracking lost with the GitHub tracker #2

New Issue
Closed
opened 2026-07-05 03:41:11 +00:00 by Mihaela · 0 comments
Mihaela commented 2026-07-05 03:41:11 +00:00 (Migrated from codeberg.org)
Copy Link

Status (2026-07-05)

Open. The Codeberg tracker started empty; all prior issue history was lost when the GitHub repo was deleted.

README.md and docs/roadmap.md cite many issue numbers from the old tracker (#130, #139, #145 through #148, #167, #175 through #178, and more). The 0.4.8 repoint swapped their host to Codeberg mechanically, so the links now point at issue numbers that do not exist here, and docs/roadmap.md still says "Pin #167 on GitHub".

Per the issue-tracker discipline, a roadmap may not cite nonexistent issues.

Fix:

  • Recreate the load-bearing epics on Codeberg (at minimum the production-readiness epic that was #167, the XSTS false-negative buckets, and the performance epic), each with a current dated status body.
  • Update README.md and docs/roadmap.md to the new numbers and drop the "on GitHub" phrasing.
  • Anything not worth recreating gets its reference removed rather than left dangling.
## Status (2026-07-05) Open. The Codeberg tracker started empty; all prior issue history was lost when the GitHub repo was deleted. `README.md` and `docs/roadmap.md` cite many issue numbers from the old tracker (#130, #139, #145 through #148, #167, #175 through #178, and more). The 0.4.8 repoint swapped their host to Codeberg mechanically, so the links now point at issue numbers that do not exist here, and `docs/roadmap.md` still says "Pin #167 on GitHub". Per the issue-tracker discipline, a roadmap may not cite nonexistent issues. Fix: - Recreate the load-bearing epics on Codeberg (at minimum the production-readiness epic that was #167, the XSTS false-negative buckets, and the performance epic), each with a current dated status body. - Update `README.md` and `docs/roadmap.md` to the new numbers and drop the "on GitHub" phrasing. - Anything not worth recreating gets its reference removed rather than left dangling.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: NodetteHQ/PureXML#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?