Skip to content

Resolve the release-policy finding: 2.2.0's PyPI release was intentional #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
EONRaider merged 1 commit into from
Sep 4, 2026
+15 −6
Merged

Resolve the release-policy finding: 2.2.0's PyPI release was intentional #154

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,8 +78,15 @@ methodology, and updated 1.1/1.2/1.6 figures.
published there); left unfixed pending a maintainer decision on
whether 2.2.0's publication was intentional, since fixing the prose
first would paper over a real process question.

## [2.2.0] - 2026-09-04
- **Resolved the seventh finding above: 2.2.0's PyPI publication was
confirmed intentional.** The Roadmap section's "per the roadmap's own
release policy, only 2.0.0 was an actual PyPI release" is now
"the roadmap's original 'only at a major version bump' release policy
wasn't actually held to: both 2.0.0 and 2.2.0 — a minor release — are
on PyPI," and the roadmap table's 2.2.0 row gained the same
**released** marker 2.0.0 already carried. Issue #107, the source
both docs draw this from, updated its own stated policy line with a
dated correction rather than silently rewriting history.

### Added
- **Typed accessors for every enum-backed field.** `_enums.py` defines
Expand Down
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -394,14 +394,16 @@ comparative-claims embargo lift that closed it out:
| [1.4.0](https://github.com/EONRaider/NETProtocols/issues/103) | Decode performance |
| [2.0.0](https://github.com/EONRaider/NETProtocols/issues/104) | A public protocol registry, a shipped chain walker, flow keys — **released** |
| [2.1.0](https://github.com/EONRaider/NETProtocols/issues/105) | Typed accessors and pattern-matching ergonomics |
| [2.2.0](https://github.com/EONRaider/NETProtocols/issues/106) | Universal round-trip properties, nightly fuzzing, a pcap reader |
| [2.2.0](https://github.com/EONRaider/NETProtocols/issues/106) | Universal round-trip properties, nightly fuzzing, a pcap reader — **released** |

Everything through 2.2.0 has landed on `master`, plus a since-landed
decode-throughput fix
([#147](https://github.com/EONRaider/NETProtocols/issues/147), not yet
versioned); per the roadmap's own release policy, only 2.0.0 was an
actual PyPI release, and the comparative claims above draw on the
finished tree. New planned work
versioned). 2.1.0's and 1.3.1/1.4.0's work shipped folded into 2.0.0
and 2.2.0 rather than as their own versions, but the roadmap's original
"only at a major version bump" release policy wasn't actually held to:
both 2.0.0 and 2.2.0 — a minor release — are on PyPI, and the
comparative claims above draw on the finished tree. New planned work
will open fresh issues rather than restating a list here, so this
section stays accurate without upkeep. The wave before this one — TCP
and IPv4 option parsing, ICMP message bodies, NDP, IPv6
Expand Down
Loading