Repository navigation
docs: roll ROADMAP tracker state after emptying the issue tracker - #1053
Merged
Merged
Conversation
…26-09-29) The same day as the rc.78 cut, the last four open issues were closed — #1038 and #1030 (their shipped halves are the rc.78 record: the size epic's stage 1 at −26.1 % durable, the corpus-packs records half with detached signatures) and the two carried defects #1031 (autoindex aborts on a source file that grows mid-run) and #1032 (per-segment caches unbounded until merge-retire), both closed as deferred, not fixed. The pinned pointer #298 had already been closed as abandoned and is now unpinned. The tracker is empty. ROADMAP consequences, all in this commit: - "In flight for rc.79" now says nothing is in flight; the three rc.78 riders were closed the same day as the cut. - "Open defects carried into rc.79" became "Open defects. None" with a deferred record of #1031/#1032 in plain text — plain text because the release-notes gate (check 1a) greps every issues/N link in this section against the live tracker at every cut, and both issues are now closed; linked closed issues there fail the next release branch. - The pinned-issue bullet under "Follow the roadmap" is gone (#298 is closed and unpinned; this file and the CHANGELOG are the surface). - The mail-ingest line and the corpus-hub item now state #1032/#1030's closed-as-deferred/descoped status instead of presenting them as open trackers. - The review line gains one sentence recording the same-day closure. Machine check: docs_capability_lists 15/15 locally (review-line version token v1.0.0-rc.78 and Next-release rc.79 marker unchanged).
Merge-time rule: every PR that lands on main after a tag gets its CHANGELOG citation now, not at the next cut, so the release-notes gate (check 2, prev-tag..HEAD) finds it. One Documentation entry under [Unreleased] citing PR #1053.
xerj-org
added a commit
that referenced
this pull request
Sep 30, 2026
…d packs shipped in rc.78 Both agent-facing index files still said corpus packs were "planned, no code" (landing/llms.txt:50, and the NOT-IMPLEMENTED list in landing/llms-full.txt). False since v1.0.0-rc.78 (2026-09-29): PRs #1046/#1047 (builder + rust-vulns showcase) and #1048 (signing/publish), hardened by #1049-#1051, shipped `xerj corpus build` — a declarative recipe becomes a checksummed portable pack of records (format_version refusal, licence + provenance on every record), `corpus add --from` verifies per-file SHA-256 and `--verify-sig` a detached ed25519 signature over SHA256SUMS, and the first pack is rebuilt, signed and published daily as a dated GitHub Release. The correction claims exactly what shipped, no more: it says plainly that the PRE-INDEXED half (an already-indexed bundle you mount instead of spending your own CPU-hours) and a hub directory beyond the first pack remain unbuilt — matching ROADMAP.md's corpus-hub row, which was rolled in #1053. Edits follow each file's own precedent for status rolls so nothing is restructured: llms.txt rewrites the one clause in the not-implemented caveat using the same inline pattern the line already uses for the v1.0.0-rc.77 object-storage roll, and adds docs/CORPUS_PACKS.md to the "file that proves it" tail; llms-full.txt keeps the log-mode bullet, points it at a new "left this list in v1.0.0-rc.78" paragraph modelled on the object-storage one, and keeps the list's 2026-09-26 re-check date (the new paragraph carries its own 2026-09-29 date instead of claiming a full re-check) and its ~76-char wrap. Known lag, deliberately untouched here: the linked answer page landing/answers/does-xerj-support-s3-alerting-plugins.md (and its .html twin) still carries the old "no code exists" wording; it needs its own surgical PR.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the rc.78 cut (#1052), same day: the tracker was emptied.
What happened outside the tree (recorded here so the file matches reality):
not plannedwithrecord comments — engine: reduce on-disk index size — per-block bitpacking, delta encodings, one shared term dictionary, zstd trained dictionaries #1038 (size epic: stage 1 shipped in rc.78,
5,398,478 → 3,989,254 B durable, −26.1 %; the unshipped levers re-file
per-lever when taken up), corpus/index: portable one-file bundles — indexed data that works across machines #1030 (corpus packs: records half shipped
rc.78 with detached signatures; pre-indexed half descoped pending the
three recorded risks), and the two carried defects autoindex: a source file that grows mid-run (append-only log) kills the run, is misclassified as a bulk/backend failure, and the retry advice points at the wrong fix #1031 (autoindex
aborts when a source file grows mid-run) and engine: stored_value_cache / dv_cache / id_pos_cache remain unbounded until merge-retire — the residual heap-per-doc retention after #1002 #1032 (per-segment
caches unbounded until merge-retire) — both closed as deferred, not
fixed, their repros intact in the closed issues.
In this tree — ROADMAP.md only:
closed the same day.
the autoindex: a source file that grows mid-run (append-only log) kills the run, is misclassified as a bulk/backend failure, and the retry advice points at the wrong fix #1031/engine: stored_value_cache / dv_cache / id_pos_cache remain unbounded until merge-retire — the residual heap-per-doc retention after #1002 #1032 deferred record in plain text, not links — the
release-notes gate (check 1a) greps every
issues/Nlink in thatsection against the live tracker at every cut, so linked-closed issues
there would fail the next release branch. Verified: zero
issues/NURLs in the section.
closed status instead of presenting open trackers.
tokens untouched).
Checks:
docs_capability_lists15/15 locally — the review-lineversion token (
v1.0.0-rc.78) and the Next release — rc.79 marker areunchanged. CHANGELOG
[Unreleased]entry added in the follow-up commitciting this PR, per the merge-time rule.