Add 10.2.0 changelog and release notes - #13521
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Apache Traffic Server v10.2.0 release documentation by introducing a new top-level changelog file and expanding the existing release-notes docs with v10.2 “what’s new” and upgrade guidance (including the HostDB-state-based origin retry behavior change).
Changes:
- Added a generated
CHANGELOG-10.2.0for the 10.2.0 milestone. - Added a new “What’s New in ATS v10.2” section to the release notes.
- Added a new “Upgrading to ATS v10.2” section describing incompatible/configuration changes.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| doc/release-notes/whats-new.en.rst | Adds v10.2 “what’s new”, including new features/configuration/metrics/plugins/API highlights. |
| doc/release-notes/upgrading.en.rst | Adds v10.2-specific upgrade notes, including the HostDB-state-based origin retry behavior change. |
| CHANGELOG-10.2.0 | Adds the generated v10.2.0 changelog content. |
Suppressed comments (1)
doc/release-notes/whats-new.en.rst:120
- In the list of new records.yaml settings, this entry is formatted as a literal code span while the surrounding entries use :ts:cv:. Since this is a real config record, it should be :ts:cv: for consistent linking and indexing in the docs.
* :ts:cv:`proxy.config.http.per_client.connection.exempt_list`
* :ts:cv:`proxy.config.proxy_protocol.max_header_size`
* ``proxy.config.quic.server.token_key.filename``
* :ts:cv:`proxy.config.ssl.client.cert_compression.algorithms`
* :ts:cv:`proxy.config.ssl.server.cert_compression.algorithms`
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
cmcfarlen
force-pushed
the
10.2.0-release-notes
branch
from
August 10, 2026 15:34
d7a5cad to
6f9e651
Compare
Generate CHANGELOG-10.2.0 from the 10.2.0 milestone and document the release in whats-new and upgrading. The connect retry change (apache#13102) is called out as a necessary incompatible change, since the retry limits were not previously applied according to origin state.
The PR count was 655 before five stale milestone entries were dropped; the changelog has 650. Use :ts:cv: for proxy.config.quic.server.token_key.filename, which is documented on 10.2.x even though it is absent from master, where it was first checked.
Picks up apache#13328 (shared-memory cache directory for fast restart) and apache#13418 (traffic_ctl cache clear). The shm directory gets its own section since it is a new opt-in feature with four new records and a traffic_ctl subcommand.
The Release 2 security bundle (apache#13452) landed directly on 10.2.x without public PRs, so those commits never appear in a milestone. Source them from the commit range with the changelog tool's git-range mode and append them as bare subjects, matching how CHANGELOG-10.1.4 lists them. Link the advisory from whats-new for the CVE mapping.
Three late bug fixes on 10.2.x. All are fixes with no new configuration, metrics or API surface, so only the changelog and the commit/PR counts change.
cmcfarlen
force-pushed
the
10.2.0-release-notes
branch
from
August 10, 2026 17:57
8841875 to
dc194d5
Compare
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.
Generated
CHANGELOG-10.2.0from the 10.2.0 milestone (650 PRs) and addedthe v10.2 sections to
whats-newandupgrading.Authored off
10.2.xrather than master, since master's copies of these docsdescribe changes not in this release (e.g.
ssl_multicert.yaml).Discussion needed: #13102
#13102 (Fix connect attempt retries) changes retry limits to be selected by
HostDB state, so
DOWNorigins are no longer retried at all. I documented itas a necessary incompatible change, on the grounds that the limits were not
previously applied per origin state as documented.
Two things worth confirming:
upstream/10.1.x— it still has the oldtwo-way
is_server_negative_cached()branch and noconnect_attempts_max_retries_suspect_serverrecord. If it did land there,the upgrade note should say so, since operators coming from a late 10.1.x
would already have the new behavior.
release that is otherwise meant to be compatible.
No Sphinx build locally; relying on CI for the docs build.