Document cleanup roadmap: split PR #90 and DUnitX-first#96
Open
omonien wants to merge 1 commit into
Open
Conversation
Record that AEAD architecture must be separated from ChaCha features, and that a full DUnit to DUnitX migration is the prerequisite before that work.
4 tasks
Author
Cleanup package index (for review)Hallo Markus — hier die Übersicht der sechs getrennten PRs gegen Paket A — Fundament
Paket B — Rote Suite / Produktkorrekturen
Empfohlene Reihenfolge
Bewusst nicht in diesem Paket
Details und Begründungen stehen in den jeweiligen PR-Beschreibungen und in |
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
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.
For Markus — please read this first
This PR is documentation only. It records the agreed cleanup strategy so the following product/test PRs have a shared context.
The core idea
Open contribution PR #90 (ChaCha20-Poly1305) currently mixes two independent concerns:
Merging that as one unit would force an all-or-nothing review of a large change set and make regressions hard to attribute. The roadmap therefore says:
Binding work order (short)
Why tests first?
Architecture and cipher merges need one trustworthy automated suite. Dual DUnit/DUnitX with incomplete coverage weakens the signal when we start touching cipher modes.
What to review
Docs/Cleanup-Roadmap.mdonlyRisk
None (docs only). Easy to amend later.
Note
Later PRs (DUnitX, GCM) may extend this file. This PR is the initial planning snapshot for discussion.