qttown.

Qt Town · community field guide

The Qt year

The wheel uses actual calendar dates. Colors and line patterns identify tracks; each number corresponds to an entry in the complete list.

2026

Oldest source review: 2026-10-12.

Qt 6.13 continues in 2027.

Qt release and community calendar for 2026Calendar months arranged around a wheel. Linked numbered markers show dated milestones; the list below contains event details.Build · test ·meet2026JanFebMarAprMayJunJulAugSepOctNovDec12String freeze3456Release78,9Feature freeze10111213String freeze14151617Release2122Feature freeze23241819QtCS20
Noninteractive Qt release and community calendar overview for 2026Calendar months, release and community tracks, dated points, and intervals. Use the complete calendar list below for milestone details.Qt2026JanFebMarAprMayJunJulAugSepOctNovDec
Browse the 2026 milestones

Build · test · meet. Choose a small, useful change · Gerrit · Jira · development mailing list · Qt Forum, IRC and Matrix communities

Upcoming milestones

  1. Qt 6.13 · 2026-11-20 · Planned

    Platform and module freeze

    Review the named release’s platform and module scope; coordinate proposed exceptions with the release team.

  2. Qt 6.13 · 2026-12-04 · Planned

    Feature freeze

    Finish feature integration, tests, documentation, examples, and platform readiness before the deadline; check current release guidance.

  3. Qt 6.13 · 2026-12-07 · Planned

    Branch 6.13 from dev

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

  4. Qt 6.13 · 2026-12-18 · Planned

    Beta 1

    Try the prerelease and report reproducible problems in Jira.

2027

Oldest source review: 2026-10-12.

Qt 6.13 continued from 2026.

Qt release and community calendar for 2027Calendar months arranged around a wheel. Linked numbered markers show dated milestones; the list below contains event details.Build · test ·meet2027JanFebMarAprMayJunJulAugSepOctNovDec252627String freeze28293031Release
Noninteractive Qt release and community calendar overview for 2027Calendar months, release and community tracks, dated points, and intervals. Use the complete calendar list below for milestone details.Qt2027JanFebMarAprMayJunJulAugSepOctNovDec
Browse the 2027 milestones

Build · test · meet. Choose a small, useful change · Gerrit · Jira · development mailing list · Qt Forum, IRC and Matrix communities

Upcoming milestones

  1. Qt 6.13 · 2027-01-15 · Planned

    Beta 2

    Try the prerelease and report reproducible problems in Jira.

  2. Qt 6.13 · 2027-02-02 · Planned

    Soft string freeze

    Avoid changing translatable source strings; coordinate necessary exceptions with localization.

  3. Qt 6.13 · 2027-02-09 · Planned

    String freeze

    Help translators by keeping source strings stable; follow the release’s localization workflow.

  4. Qt 6.13 · 2027-02-12 · Planned

    Beta 3

    Try the prerelease and report reproducible problems in Jira.

Qt development continues throughout the year. Qt's release documentation describes two minor releases a year as the usual framework cadence. Treat that as an overview: check the named schedule for dates, because phases can overlap and plans can change. Some Qt tools and related products have their own release schedules.

The first view covers the Qt framework's 6.11, 6.12, and 6.13 release series across 2026 and 2027, plus the announced 2026 Qt Contributors Summit. Dates and phase names come from each linked public source. Sources checked 12 October 2026; planned dates remain plans until an owning source records what happened.

A Git repository stores source history. Branches are lines of work inside repositories; release schedules describe when a named version moves through its phases. A release is not a repository, and a release schedule is not a count of distinct changes.

For an ordinary code or documentation contribution, start with the small-change guide. The Qt issue tracker is the place to report a reproducible problem. For help, use the Qt Forum or the development mailing list.

Platform module freeze

The Qt 6.13 release schedule names when platform and module work reaches this phase for that version. Scope and exceptions depend on the release; check its current plan and release-team notes before deciding whether a change can still land.

Feature freeze

Qt's feature-freeze guidance says new features should reach dev well before the freeze and have tests, documentation, examples, and platform readiness in place. Plan feature work early, then check the named release's latest guidance; a patch uploaded on the freeze date is not assured inclusion.

Branching

The QUIP 16: Branch policy (Active / Process) describes Qt framework branches. For example, the Qt 6.13 schedule lists a planned branch from dev named 6.13 for December 7, 2026. This remains a target until the schedule records completion. In the usual flow, dev continues for the next minor series while a stable branch prepares the current release; eligible fixes can be cherry-picked to that branch. The active policy also allows exceptions when no matching change exists on dev. Check the current schedule and policy before you start.

Beta

A beta is a chance to try the next release while it is still being developed. Install or build the prerelease, test the areas you use, and use the small-change guide to record a clear reproduction. Report a reproducible problem in Qt Jira. The Qt 6.12 beta announcement is an example of a release-specific testing request.

Soft string freeze

After the early betas, release teams ask contributors to avoid changing translatable source strings where possible. Finish wording changes early; if a change is needed later, check the release notice and coordinate with the Qt localization community. For example, the Qt 6.12 soft string-freeze notice asks for string stability.

String freeze

At string freeze, translators can work against more stable source text. The Qt translation workflow has its own forward-merging branch model. For example, the Qt 6.12 string-freeze notice records that release's freeze. Read the current instructions before choosing a branch.

Release candidate

Test a release candidate for final-release suitability and report blockers with clear steps to reproduce. Check the named release's announcement for current branch restrictions, then use Qt Jira for issues. For example, the Qt 6.12 RC announcement describes that release's limits.

Final release

The final release makes a named version available. Read its release notes and known issues; report problems through Qt Jira. For example, the Qt 6.12 release announcement links to that version's release information. For a proposed fix, check QUIP 16 and the relevant branch guidance to find where it belongs.

QtCS

The Qt Contributors Summit is a yearly gathering for technical and community discussions, but its timing varies. As announced on the 2026 event page, welcome activities and Qt World Summit technical sessions are on October 27, summit sessions run October 28–29, and the hacking day is October 30. As checked on 12 October 2026, these are upcoming announced dates, not a claim that the event has happened. Check the event page for its program and participation details.

The summit also brings contributors together around Qt Project Goals: shared priorities that span modules and guide community work over two years. Read the proposals and look for an area where you would like to help.

Complete calendar

Complete 2026 calendar (26 milestones)

Milestones

  1. 1

    Qt 6.11 · 3 Feb 2026 · Completed

    Soft string freeze

    Avoid changing translatable source strings; coordinate necessary exceptions with localization.

    Phase guidance: soft string freeze

    Sources and date history

    ID: qt-6-11-soft-string-freeze

  2. 2

    Qt 6.11 · 12 Feb 2026 · Completed

    String freeze

    Help translators by keeping source strings stable; follow the release’s localization workflow.

    Phase guidance: string freeze

    Sources and date history

    ID: qt-6-11-string-freeze

  3. 3

    Qt 6.11 · 18 Feb 2026 · Completed

    Beta 3

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-11-beta-3

  4. 4

    Qt 6.11 · 23 Feb 2026 · Completed

    Branch 6.11.0 from 6.11

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

    Phase guidance: branching

    Sources and date history

    ID: qt-6-11-branch-6-11-0

  5. 5

    Qt 6.11 · 2 Mar 2026 · Completed

    Release candidate

    Test whether the build is ready for final release and report reproducible blockers in Jira.

    Phase guidance: release candidate

    Sources and date history

    ID: qt-6-11-release-candidate

  6. 6

    Qt 6.11 · 23 Mar 2026 · Completed

    Final release

    Review release notes and known issues; contribute follow-up fixes for later releases.

    Phase guidance: final release

    Sources and date history

    ID: qt-6-11-final-release

  7. 7

    Qt 6.12 · 15 May 2026 · Completed

    Platform and module freeze

    Review the named release’s platform and module scope; coordinate proposed exceptions with the release team.

    Phase guidance: platform module freeze

    Sources and date history

    ID: qt-6-12-platform-module-freeze

  8. 8

    Qt 6.12 · 2 Jun 2026 · Completed

    Branch 6.12 from dev

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

    Phase guidance: branching

    Sources and date history

    ID: qt-6-12-branch-from-dev

  9. 9

    Qt 6.12 · 2 Jun 2026 · Completed

    Feature freeze

    Finish feature integration, tests, documentation, examples, and platform readiness before the deadline; check current release guidance.

    Phase guidance: feature freeze

    Sources and date history

    ID: qt-6-12-feature-freeze

  10. 10

    Qt 6.12 · 11 Jun 2026 · Completed

    Beta 1

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-12-beta-1

  11. 11

    Qt 6.12 · 14 Jul 2026 · Completed

    Beta 2

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-12-beta-2

  12. 12

    Qt 6.12 · 11 Aug 2026 · Completed

    Soft string freeze

    Avoid changing translatable source strings; coordinate necessary exceptions with localization.

    Phase guidance: soft string freeze

    Sources and date history

    ID: qt-6-12-soft-string-freeze

  13. 13

    Qt 6.12 · 18 Aug 2026 · Completed

    String freeze

    Help translators by keeping source strings stable; follow the release’s localization workflow.

    Phase guidance: string freeze

    Sources and date history

    ID: qt-6-12-string-freeze

  14. 14

    Qt 6.12 · 4 Sep 2026 · Completed

    Beta 4

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-12-beta-4

  15. 15

    Qt 6.12 · 9 Sep 2026 · Completed

    Branch 6.12.0 from 6.12

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

    Phase guidance: branching

    Sources and date history

    ID: qt-6-12-branch-6-12-0

  16. 16

    Qt 6.12 · 18 Sep 2026 · Completed

    Release candidate

    Test whether the build is ready for final release and report reproducible blockers in Jira.

    Phase guidance: release candidate

    Sources and date history

    ID: qt-6-12-release-candidate

  17. 17

    Qt 6.12 · 30 Sep 2026 · Completed

    Final release

    Review release notes and known issues; contribute follow-up fixes for later releases.

    Phase guidance: final release

    Sources and date history

    ID: qt-6-12-final-release

  18. 18

    Qt Contributors Summit 2026 · 27 Oct 2026 · Announced

    Qt World Summit and welcome event

    See the edition page for the welcome program and participation details.

    Phase guidance: qtcs

    Sources and date history

    ID: qtcs-2026-welcome-day

  19. 19

    Qt Contributors Summit 2026 · 28 Oct 2026–29 Oct 2026 · Announced

    Qt Contributors Summit sessions

    Review the program and join the technical and community discussions.

    Phase guidance: qtcs

    Sources and date history

    ID: qtcs-2026-sessions

  20. 20

    Qt Contributors Summit 2026 · 30 Oct 2026 · Announced

    Hacking day

    Check the edition page for the hacking-day plan.

    Phase guidance: qtcs

    Sources and date history

    ID: qtcs-2026-hacking-day

  21. 21

    Qt 6.13 · 20 Nov 2026 · Planned

    Platform and module freeze

    Review the named release’s platform and module scope; coordinate proposed exceptions with the release team.

    Phase guidance: platform module freeze

    Sources and date history

    ID: qt-6-13-platform-module-freeze

  22. 22

    Qt 6.13 · 4 Dec 2026 · Planned

    Feature freeze

    Finish feature integration, tests, documentation, examples, and platform readiness before the deadline; check current release guidance.

    Phase guidance: feature freeze

    Sources and date history

    ID: qt-6-13-feature-freeze

  23. 23

    Qt 6.13 · 7 Dec 2026 · Planned

    Branch 6.13 from dev

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

    Phase guidance: branching

    Sources and date history

    ID: qt-6-13-branch-from-dev

  24. 24

    Qt 6.13 · 18 Dec 2026 · Planned

    Beta 1

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-13-beta-1

Dates to confirm

Qt 6.11

  • 32

    Qt 6.11 · Date disputed

    Beta 2 date disputed

    Keep the schedule conflict visible until a public source resolves it.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-11-beta-2

    • original plan source · 2026-01-16 · revision oldid=46737 · checked 2026-10-12
    • claim source · claim: “Realized column: 15.01.2025” · revision oldid=46737 · checked 2026-10-12

Qt 6.12

  • 33

    Qt 6.12 · Date disputed

    Beta 3 date disputed

    Keep the conflicting schedule date visible until a public source resolves it.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-12-beta-3

    • original plan source · 2026-08-18 · revision oldid=46712 · checked 2026-10-12
    • updated plan source · 2026-08-20 · revision oldid=46712 · checked 2026-10-12
    • claim source · claim: “Realized column: 20.02.2026” · revision oldid=46712 · checked 2026-10-12

Cross-year context

  • 25

    Qt 6.13 · 15 Jan 2027 · Planned

    Outside 2026; shown as cross-year context.

    Beta 2

    Try the prerelease and report reproducible problems in Jira.

    Open canonical entry

    Sources and date history

    ID: qt-6-13-beta-2

Complete 2027 calendar (7 milestones)

Milestones

  1. 25

    Qt 6.13 · 15 Jan 2027 · Planned

    Beta 2

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-13-beta-2

  2. 26

    Qt 6.13 · 2 Feb 2027 · Planned

    Soft string freeze

    Avoid changing translatable source strings; coordinate necessary exceptions with localization.

    Phase guidance: soft string freeze

    Sources and date history

    ID: qt-6-13-soft-string-freeze

  3. 27

    Qt 6.13 · 9 Feb 2027 · Planned

    String freeze

    Help translators by keeping source strings stable; follow the release’s localization workflow.

    Phase guidance: string freeze

    Sources and date history

    ID: qt-6-13-string-freeze

  4. 28

    Qt 6.13 · 12 Feb 2027 · Planned

    Beta 3

    Try the prerelease and report reproducible problems in Jira.

    Phase guidance: beta

    Sources and date history

    ID: qt-6-13-beta-3

  5. 29

    Qt 6.13 · 18 Feb 2027 · Planned

    Branch 6.13.0 from 6.13

    Use the named stable branch for eligible fixes and continue next-cycle feature work on dev; check release-specific restrictions.

    Phase guidance: branching

    Sources and date history

    ID: qt-6-13-branch-6-13-0

  6. 30

    Qt 6.13 · 26 Feb 2027 · Planned

    Release candidate

    Test whether the build is ready for final release and report reproducible blockers in Jira.

    Phase guidance: release candidate

    Sources and date history

    ID: qt-6-13-release-candidate

  7. 31

    Qt 6.13 · 17 Mar 2027 · Planned

    Final release

    Prepare to review release notes and known issues, then contribute follow-up fixes when the release is available.

    Phase guidance: final release

    Sources and date history

    ID: qt-6-13-final-release

Cross-year context

  • 24

    Qt 6.13 · 18 Dec 2026 · Planned

    Outside 2027; shown as cross-year context.

    Beta 1

    Try the prerelease and report reproducible problems in Jira.

    Open canonical entry

    Sources and date history

    ID: qt-6-13-beta-1