pmaports/docs/releases/timeline.md
Oliver Smith ad05a1b83b
docs/releases/timeline: add numbers before phases
Adjust the timeline docs and release infrastructure template to have
numbers before the phases. This makes clearer where the next phase
begins in the long infrastructure issue template.

Signed-off-by: Oliver Smith <ollieparanoid@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8815>
2026-06-15 19:23:56 +00:00

1.8 KiB

Release Timeline

The calendar week (CW) numbers in this document get updated before the next release cycle starts. Get the current CW with date +%V. During the release cycle we try to follow this plan closely, but it can happen that we run over the planned CWs.

1. Pre-Build

CW 21 (2026-05-18 - 2026-05-24)

Release branches are not yet in feature freeze, but we should avoid making major changes to main.

Team:

  • Create the infrastructure issue (which has more detailed tasks for the team for each phase, the document here just gives a rough overview).
  • Create the release branch in pmaports.
  • Start building of binary packages early, so we can get through it for sure.

2. Branch

CW 22 (2026-05-25 - 2026-05-31), CW 23 (2026-06-01 - 2026-06-07)

The release branch is in feature freeze:

We can cherry pick fixes where it makes sense, but can't add features to the release branch anymore (exceptions can be made if there is a good reason).

Team:

  • Rebase the release branch on main once
  • Build binary packages and images (configure BPO for that)

3. Test

CW 24 (2026-06-08 - 2026-06-14)

Maintainers:

  • Test your devices and UIs (test yourself if you can and/or coordinate with the Testing Team)
  • Report back in the issue (template for devices)
  • Fix stuff that is broken by creating MRs against pmaports main and assigning the backport-to-YY.MM label

4. Release

CW 25 (2026-06-15 - 2026-06-21)

Team:

  • Write the release blog post.

Team + Maintainers:

  • Celebrate with party hats and get wasted.