Modernize wiki: branch-aware release process, archive May 2026 summit, add Design Documents
Release Process: the release instructions only described the autotools flow, which
is correct for 9.2.x but not for 10.x and later. Document both: 9.2.x keeps
configure.ac (TS_VERSION_S / TS_VERSION_N) with 'make changelog' and
'RC=1 make rel-candidate'; 10.x and later set the version in CMakeLists.txt and
use the equivalent cmake targets. Note that the CMake build has no changelog
target. Drop the reference to trafficserver.spec, which no longer exists on any
active branch. Drop the hardcoded version list in favor of the Downloads page and
roadmap so it cannot go stale.
ATS Summit May 2026: mark as concluded, remove the closed call for talks and the
pending meeting link.
Getting Started: complete the CMake preset table (asan, tsan, hardened,
autest-uds) and note the ci-* and branch-* families.
Design Documents: new page covering in-flight proposals, an index of accepted
designs in the developer guide, and how to take a design from draft to published.
Footer: copyright 2025 -> 2026.
Make prerequisite package lists into runnable install commands
- Add actual package manager commands (dnf install, apt-get install, apk add, brew install, pkg install)
- Add git to all package lists (was missing)
- Add zlib-devel for Fedora/RHEL (was missing, cmake fails without it)
- Split Fedora and RHEL/Rocky/Alma into separate sections (RHEL needs EPEL + CRB for ninja-build)
- Fix Alpine: remove libexecinfo-dev (no longer exists), use openssl-dev instead of libressl-dev
- Add note about Alpine musl libc compatibility
- Fix FreeBSD to use pkg install with correct package names
Fill in Developer Guide wiki pages
- Getting Started: prerequisites by OS, CMake presets, build/install,
editor setup, Docker CI images
- Coding Style: C++20 standard, formatting rules, naming conventions,
brace style, pointer alignment, comment philosophy, license headers,
debug logging patterns
- Contributing: issue filing, PR workflow, branching, labels, backports,
WIP PRs, communication channels
- Code Review: what reviewers look for, approval requirements, required
CI checks from .asf.yaml, squash merge policy, committer responsibilities
- Testing: Catch2 unit tests, AuTest end-to-end tests, running tests
locally and in parallel, writing new tests with Proxy Verifier,
sandbox structure, test coverage
Reorganize wiki structure with developer handbook pages
Add skeleton pages for a comprehensive developer wiki:
- Home: landing page with navigation and links
- Getting Started: build setup and dev environment
- Coding Style: formatting, naming, best practices
- Contributing: PR workflow and issue filing
- Code Review: review process and merge policy
- Testing: unit tests, AuTests, coverage
- Continuous Integration: CI checks and failure debugging
- Architecture Overview: event model, threading, state machine
- Release Process: branches, versioning, release management
- _Sidebar: persistent navigation for all pages
Update Home page from bare welcome to organized hub.
Update footer copyright year.