LoginSign Up
← Back to all sparks
A

Ansible

INFRA · APIS
Velocity5.0

Agentless IT automation and configuration management engine

www.ansible.com ↗

Four maintenance branches move in lockstep, with the actual changes hidden behind a link.

maintenancemulti-branchrelease-candidatesbackportspackaging
◆Current state
ansible-core is in pure maintenance mode across four concurrent branches — 2.18, 2.19, 2.20 and 2.21 — each cut on the same day within minutes of the others. The published release notes carry no feature text at all: every entry is a stub pointing at an external changelog plus wheel and tarball checksums. From the feed alone, the only observable signal is cadence and branch topology, not capability.
◆Where it's heading
The pattern is a stable, heavily backported LTS-style train: release candidates for all live branches go out together on one day, then the finals land as a batch a week later. Two of the four RCs cut on 3 August (2.18.19rc1, 2.19.12rc1) promoted to finals on 10 August, while 2.20.8 and 2.21.3 remain in candidate state. That rhythm suggests a release process driven by a shared backport queue rather than per-branch feature work.
◆Prediction
Expect 2.20.8 and 2.21.3 to promote from rc1 to final on the next batch date, with a fresh round of rc1 tags across all four branches shortly after. What lands inside them isn't visible from these entries.

◆Recent moves

  1. 8d ago

    ansible-core 2.19.12 final release

    Promotes the 2.19.12 candidate cut a week earlier to a final release. The entry itself carries only artifact sizes and SHA-256 sums, so the substance sits behind the linked changelog.

    View source ↗
  2. 8d ago

    ansible-core 2.18.19 final release

    The 2.18 branch's twin of the same batch, tagged 91 seconds after 2.19.12. Same stub-plus-checksums shape, confirming the two branches are cut by one automated process.

    View source ↗
  3. 15d ago

    ansible-core 2.21.3 release candidate 1

    First release candidate on the newest maintained branch, part of the 3 August four-branch RC batch. No user-visible change is described in the entry.

    View source ↗
  4. 15d ago

    ansible-core 2.20.8 release candidate 1

    The 2.20 branch candidate from the same batch, tagged a minute before 2.21.3rc1. Still awaiting promotion to final as of the latest entries.

    View source ↗
  5. 15d ago

    ansible-core 2.19.12 release candidate 1

    The candidate that became the 2.19.12 final a week later — the pair shows the branch's RC-to-release lag is about seven days.

    View source ↗
  6. 15d ago

    ansible-core 2.18.19 release candidate 1

    Oldest-branch candidate in the 3 August batch, later promoted to 2.18.19. Its content is identical in structure to its three siblings.

    View source ↗