LoginSign Up
← Back to all sparks
A

Asterisk

MEETINGS
Velocity5.0

Open-source framework for building voice, video and PBX communications.

www.asterisk.org ↗

The three-branch cycle closes: 20, 22 and 23 all promote to final with the same 28-issue set.

backport disciplinemulti-branch releasesmaintenance cycletelephony corerelease cadence
◆Current state
The release round that opened on August 7 has finished. Asterisk 20.21.0, 22.11.0 and 23.5.0 all tagged within a minute of each other, each carrying 39 commits from 16 authors, 28 resolved issues and zero security advisories. The counts are identical across all three branches, which is the same backport-in-lockstep pattern the certified track and the June security round both followed.
◆Where it's heading
Nothing about the shape has changed: three mainline branches plus a certified track, one fix set, promoted together. The rc1-to-rc2-to-final progression narrowed from 27 issues to a single websocket segfault fix and then closed, which is a cycle converging on schedule. Release bodies still publish counts and links rather than user-facing notes, so the feed measures release discipline rather than product direction.
◆Prediction
Expect the certified track to pick up this same fix set in its next cert release, following the lag it showed after the June round. The next mainline round should open with rc1 tags on all three branches again.

◆Recent moves

  1. 16d ago

    22.11.0 promotes to final with 28 issues resolved

    The 22 branch closes the August cycle, carrying the 27-issue rc1 set plus the websocket segfault fix from rc2. Substantive community-reported maintenance, with no advisories and no feature text in the body.

    View source ↗
  2. 16d ago

    23.5.0 closes the cycle on the newest mainline branch

    The current mainline branch takes the same 39-commit, 28-issue set at the same minute as its siblings. It is the lead branch of the round only by number; the content is identical to the 20 and 22 tags.

    View source ↗
  3. 16d ago

    20.21.0 carries the same fix set back to the LTS line

    The oldest supported mainline branch gets the identical 28-issue set, continuing the practice of landing one round everywhere at once. For operators pinned to 20, this is the same maintenance the newer branches received.

    View source ↗
  4. 23d ago

    23.5.0-rc2: single fix for a websocket PONG segfault

    A one-commit candidate closing issue 2085, a segfault in res_http_websocket when a server receives a PONG frame. It is the last narrowing step before the final tag that has now shipped.

    View source ↗
  5. 23d ago

    20.21.0-rc2 takes the same one-commit websocket fix

    The 20 branch mirror of the rc2 candidate, identical down to the author and issue number. It exists to keep the branches in step ahead of the joint final promotion.

    View source ↗
  6. 23d ago

    22.11.0-rc2 mirrors the websocket PONG crash fix

    The third copy of the same single-commit candidate. Three near-identical rc2 entries in one window are an artifact of the branch matrix, not three separate pieces of work.

    View source ↗