Development¶
Development happens in the main linux-tcp-cc repository.
Branch model¶
Each supported Linux LTS series has a long-lived branch. The current branch is 6.18.y.
Stable patch updates are reviewed as ordinary pull requests and release tags match the pinned upstream Linux patch level.
Maintenance boundary¶
Project-specific work should remain concentrated around:
- the userspace architecture;
- host runtime and lifecycle;
- TUN / packet device;
- control API;
- build/configuration;
- narrow compatibility shims for upstream API drift.
The following upstream networking implementation areas are protected during normal porting:
net/ipv4/tcp_bbr.cnet/ipv4/tcp_rate.c- Linux TCP recovery core
net/sched/sch_fq.c
Start with these documents¶
- Current architecture
- Repository documentation index
- Configuration contract
- M8 network qualification
- M10 memory lifecycle
- M11 CPU efficiency
- Published evidence
Website policy¶
This documentation site should stay intentionally small.
Implementation contracts and evidence are canonical in the main repository. The website should summarize and navigate them rather than maintain a second, more decorative source of truth.