Repository navigation
docs(pep): stale status lines and a redundant Mermaid chain in pep.rst #2564
Description
From the 2026-11-01 conventions audit, re-verified on 73add05a3. process.rst, "The PEP Discussion, Kept Current": pep.rst is the source of truth for where each wave stands. documentation.rst, "Mermaid for Flows": do not redraw a graph another page already has.
- Delivery Sequence (
docs/source/contributing/pep.rst): DCCP is "blocked on :issue:2479for its pseudo-header checksum". feat(protocols): add the IP_Pseudo pseudo-protocol for the IP pseudo-header (#2471) #2479 is a merged pull request; DCCP implementation, with the DCCP checksum over the IP pseudo-header #2489 is blocked on the checksum wave (ICMP/ICMPv6 checksum verification (deferred from #2446) #2470). - "Done ahead of wave 2" (
pep.rst, under "Delivery Sequence"): NETLINK, IPGRE, IP6GRE, IEEE80211_RADIOTAP and FRAD "have no dissector of their own, tracked as :issue:2460".pcapkit/protocols/link/frad.py,gre.pyandnetlink.pyexist and Dissectors for non-ethertype ARPHRD types on LINUX_SLL/SLL2 (NETLINK/IPGRE/IP6GRE/802.11 radiotap/FRAD) #2460 is closed; only radiotap is missing, tracked by 802.11 radiotap dissector for IEEE80211_RADIOTAP on LINUX_SLL/SLL2 #2502. - "Release Plan — 1.5.0 in Two Steps" (
pep.rst): the.. mermaid::draws push -> Unit Tests -> Vendor Update -> Create Release, which the sentence above it states andworkflows.rstdraws with the same node labels and edges.
Fix: correct both status lines and drop the graph. Discussion #106 carries neither stale line, so it needs no correction for them.
Blocked: #2528, #2542, #2543 and #2544 edit pep.rst; unblocks when all four merge (gh pr view <n> --json state -q .state prints MERGED).
Activity
JarryShaw commentedon Nov 1, 2026
#2528, #2542, #2543 and #2544 have merged, but the DCCP (#2489) and TLS-extension (#2514) fix rounds both edit pep.rst. Blocked: this unblocks when both of their PRs merge (
gh pr view <n> --json state -q .stateprintsMERGED).JarryShaw commentedon Nov 2, 2026
#2593 (DCCP) and #2595 (TLS extensions) have merged, so nothing else is editing pep.rst's status lines. Unblocked. A worker is fixing the lines listed here and re-checking every status line on the page against
main. #2561 still edits one citation on the page, so the worker leaves that line alone.JarryShaw commentedon Nov 2, 2026
The status-line fix is done locally. A docs-only commit on top of current
mainbrings every status line on pep.rst into line withmain. That includes the ARPHRD dissectors, Deterministic Construction Arguments (scoped for 1.6.0, #2594), DTLS reassembly, the TLS/DTLS port bindings, and the GRE and IGMP checksum gap, now #2618. The redundant Mermaid chain is removed in favour of workflows.rst's graph.Needs deciding: does pep.rst declare wave 2 closed? Every deliverable the page lists for wave 2 has merged.
Recommendation: 1. The page tracks what is finished, and leaving a finished wave open makes it read as stale again. The commit leaves the wave as it stands until you answer.
JarryShaw commentedon Nov 2, 2026
take 1
docs(pep): correct stale status lines and drop the redundant release …
JarryShaw commentedon Nov 2, 2026
Landed on
mainas83f05f5b4, a docs-only commit after a Sonnet review and one fix round. Every status line on pep.rst now matchesmain.IEEE802_11and keeps its optional fields for feat(link): decode radiotap's optional fields #2576.One judgement call to check: the Mobility Header item read "queued behind wave 2". It was not a "wave 2 or 3" item, so it now reads "sequenced after wave 2" rather than "wave 3". Closing.
docs(changelog): fold pad_length, the shared contextvars and the role…