FlagOS 2.2 Release Tracking | 2.2 版本发布追踪

Tracking issue for the **FlagOS 2.2** release cycle. Subscribe (👁 Subscribe button) to get freeze reminders and progress updates.

## 📅 Key dates / 关键日期

Per the branch diagram above, 2.2 stabilizes through three release candidates. Each rc is cut from `main`, takes bugfixes directly, and is merged back to `main`.

| Date | Event |
|------|-------|
| 2026-08-17 | Recommended FEP submission cutoff (2-week review SLA) / FEP 建议提交截止(评审需约 2 周) |
| **2026-08-31** | **Feature Freeze — rc0 cut** — FEPs merged + feature code submitted / FEP 已合入,特性代码已提交;rc0 拉分支 |
| 2026-09-04 | RC0 + test report published (1 week stabilization) / 发布 RC0 及测试报告 |
| **2026-09-07** | **rc1 cut** / rc1 拉分支 |
| 2026-09-11 | RC1 + test report published (1 week stabilization) / 发布 RC1 及测试报告 |
| **2026-09-14** | **rc2 cut** / rc2 拉分支 |
| 2026-09-24 | rc2 stabilization ends (2 weeks); `Hotfix` only past this point / rc2 稳定期结束,之后仅接受 hotfix |
| **2026-09-28** | **GA — Go/No-Go** 🚀 |

Branch mechanics / 分支规则: bugfixes land on the active rc branch and are merged back to `main`; feature work continues on `main` between rc cuts. After the rc2 window closes on 09-24, only hotfixes reach the release branch.

Authoritative schedule (changes via PR): [release/2.2/schedule.md](https://github.com/flagos-ai/community/blob/main/release/2.2/schedule.md) · [中文](https://github.com/flagos-ai/community/blob/main/release/2.2/schedule_CN.md)

## 📋 FEP progress / FEP 进度

FEP delivery status is tracked in one place — the **[FlagOS 2.2 milestone](https://github.com/flagos-ai/community/milestone/2)**, which holds one tracking issue per FEP (`[FEP-XXXX] ... tracking`, assigned to the FEP Owner, closed when the FEP reaches `Implemented`). Board view: [FEP Tracker](https://github.com/orgs/flagos-ai/projects/6/views/1?layout=board&groupedBy%5BcolumnId%5D=365272770).

该清单不在本 issue 内手工维护：每个 FEP 一个 tracking issue，挂在 milestone 上，Owner 认领，FEP 达到 `Implemented` 时关闭。看 milestone 即看进度。

FEP Owners: set `Target Version: FlagOS 2.2` in your FEP header, add the `target/2.2` label; on merge a tracking issue is created and attached to the milestone. Merging before Feature Freeze puts the FEP into 2.2; graduation (`Implemented`) requires acceptance during the testing window.

## 🧪 Test matrix / 测试矩阵

Maintained here per FEP as tracking issues are created; final snapshot at Feature Freeze. / 每个 FEP 的 tracking issue 创建时在此增加一行,特性冻结日定稿。

| FEP | Tracking issue | Test Plan |
|-----|----------------|-----------|
| _added as tracking issues are created_ | | |

## ⚠️ Freeze rules / 冻结规则

- **08-31 Feature Freeze** closes both 2.2 doors at once: FEP merge into 2.2 and 2.2 feature code. After it: acceptance testing, bug fixes, tuning, and FEP doc updates only — no new 2.2 feature code; feature work for later releases continues on `main`. / 特性冻结同时关上 2.2 的两扇门——FEP 合入与 2.2 特性代码;之后只做验收、修复、调优和 FEP 文档更新,不再进 2.2 特性代码,后续版本的特性开发在 `main` 上继续。
- Merged FEPs that miss the freeze are `Deferred`: tracking issue re-milestoned (not closed), `target/2.2` label swapped by the Release Manager. / 错过冻结的 FEP 顺延:tracking issue 移至下一 milestone,`target/2.2` 标签由 Release Manager 更换。
- Exception channel: `[URGENT]` fast-track per [REVIEW_GUIDE §7](https://github.com/flagos-ai/community/blob/main/fep/REVIEW_GUIDE.md#7-urgent-fep-channel), TSC approval required.