# The Qt year A simple view of Qt release phases and ways to contribute throughout the year. Snapshot: `6569b73d1aca6e4f521a0a89d707b386dbff92935491f05b82adf360d22f65ce` Date range: 2026-01-01 – 2026-11-11 UTC (inclusive). Built: 2026-11-11T17:39:37Z Repository coverage: 46 of 46 declared top-level modules, plus qt5.git. Statistics follow each module's declared development branch. The independent project catalog includes Qt Creator on its selected ref; other projects and unselected refs remain gaps. Nested third-party dependencies and release-only activity are outside this inventory. Oldest successful repository source check: 2026-11-11T17:38:44.324Z. Managed collection fetches declared refs directly from canonical Qt repositories. [Qt Town home](index.md) · [Get started](get-started.md) · [Find a reviewer](reviewers.md) · [Activity](activity.md) · [Contributors](contributors.md) · [The Qt year](year.md) · [Goals](goals.md) · [Governance](governance.md) · [How it works](methodology.md) ## Qt release and community calendar The wheel plots reviewed date-only milestones on the calendar year. Release series and community events have separate tracks; each number corresponds to an entry in the complete list. Planned dates remain plans, and disputed or unannounced dates have no wheel position. ## 2026 **Oldest relevant source review: 2026-10-12.** | Track | Type | Pattern | | --- | --- | --- | | Qt 6\.11 | release | dotted | | Qt 6\.12 | release | dashed | | Qt 6\.13 | release | solid | | Qt Contributors Summit 2026 | community | dotted | Qt 6\.13 continues in [2027](year.md#2027). Months follow the date positions around the wheel. The complete dated list follows; entries are ordered by date, with stable IDs breaking same-day ties. - **1.** **2026-02-03 · Qt 6\.11 · Completed** — [Soft string freeze](#soft-string-freeze). Avoid changing translatable source strings; coordinate necessary exceptions with localization\. ID: `qt-6-11-soft-string-freeze`. - [original plan source]() — 2026-02-03 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-02-03 — revision oldid=46737 — checked 2026-10-12 - **2.** **2026-02-12 · Qt 6\.11 · Completed** — [String freeze](#string-freeze). Help translators by keeping source strings stable; follow the release’s localization workflow\. ID: `qt-6-11-string-freeze`. - [original plan source]() — 2026-02-10 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-02-12 — revision oldid=46737 — checked 2026-10-12 - **3.** **2026-02-18 · Qt 6\.11 · Completed** — [Beta 3](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-11-beta-3`. - [original plan source]() — 2026-02-13 — revision oldid=46737 — checked 2026-10-12 - [updated plan source]() — 2026-02-18 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-02-18 — revision oldid=46737 — checked 2026-10-12 - **4.** **2026-02-23 · Qt 6\.11 · Completed** — [Branch 6\.11\.0 from 6\.11](#branching). Use the named stable branch for eligible fixes and continue next\-cycle feature work on dev; check release\-specific restrictions\. ID: `qt-6-11-branch-6-11-0`. - [original plan source]() — 2026-02-19 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-02-23 — revision oldid=46737 — checked 2026-10-12 - **5.** **2026-03-02 · Qt 6\.11 · Completed** — [Release candidate](#release-candidate). Test whether the build is ready for final release and report reproducible blockers in Jira\. ID: `qt-6-11-release-candidate`. - [original plan source]() — 2026-02-27 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-03-02 — revision oldid=46737 — checked 2026-10-12 - **6.** **2026-03-23 · Qt 6\.11 · Completed** — [Final release](#final-release). Review release notes and known issues; contribute follow\-up fixes for later releases\. ID: `qt-6-11-final-release`. - [original plan source]() — 2026-03-17 — revision oldid=46737 — checked 2026-10-12 - [updated plan source]() — 2026-03-23 — revision oldid=46737 — checked 2026-10-12 - [realized source]() — 2026-03-23 — revision oldid=46737 — checked 2026-10-12 - **7.** **2026-05-15 · Qt 6\.12 · Completed** — [Platform and module freeze](#platform-module-freeze). Review the named release’s platform and module scope; coordinate proposed exceptions with the release team\. ID: `qt-6-12-platform-module-freeze`. - [original plan source]() — 2026-05-15 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-05-15 — revision oldid=46712 — checked 2026-10-12 - **8.** **2026-06-02 · Qt 6\.12 · Completed** — [Branch 6\.12 from dev](#branching). Use the named stable branch for eligible fixes and continue next\-cycle feature work on dev; check release\-specific restrictions\. ID: `qt-6-12-branch-from-dev`. - [original plan source]() — 2026-06-01 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-06-02 — revision oldid=46712 — checked 2026-10-12 - **9.** **2026-06-02 · Qt 6\.12 · Completed** — [Feature freeze](#feature-freeze). Finish feature integration, tests, documentation, examples, and platform readiness before the deadline; check current release guidance\. ID: `qt-6-12-feature-freeze`. - [original plan source]() — 2026-05-29 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-06-02 — revision oldid=46712 — checked 2026-10-12 - **10.** **2026-06-11 · Qt 6\.12 · Completed** — [Beta 1](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-12-beta-1`. - [original plan source]() — 2026-06-11 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-06-11 — revision oldid=46712 — checked 2026-10-12 - [announcement source]() — 2026-06-12 — checked 2026-10-12 - **11.** **2026-07-14 · Qt 6\.12 · Completed** — [Beta 2](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-12-beta-2`. - [original plan source]() — 2026-07-16 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-07-14 — revision oldid=46712 — checked 2026-10-12 - **12.** **2026-08-11 · Qt 6\.12 · Completed** — [Soft string freeze](#soft-string-freeze). Avoid changing translatable source strings; coordinate necessary exceptions with localization\. ID: `qt-6-12-soft-string-freeze`. - [original plan source]() — 2026-08-11 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-08-11 — revision oldid=46712 — checked 2026-10-12 - **13.** **2026-08-18 · Qt 6\.12 · Completed** — [String freeze](#string-freeze). Help translators by keeping source strings stable; follow the release’s localization workflow\. ID: `qt-6-12-string-freeze`. - [original plan source]() — 2026-08-18 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-08-18 — revision oldid=46712 — checked 2026-10-12 - **14.** **2026-09-04 · Qt 6\.12 · Completed** — [Beta 4](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-12-beta-4`. - [updated plan source]() — 2026-09-04 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-09-04 — revision oldid=46712 — checked 2026-10-12 - **15.** **2026-09-09 · Qt 6\.12 · Completed** — [Branch 6\.12\.0 from 6\.12](#branching). Use the named stable branch for eligible fixes and continue next\-cycle feature work on dev; check release\-specific restrictions\. ID: `qt-6-12-branch-6-12-0`. - [original plan source]() — 2026-08-28 — revision oldid=46712 — checked 2026-10-12 - [updated plan source]() — 2026-09-04 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-09-09 — revision oldid=46712 — checked 2026-10-12 - **16.** **2026-09-18 · Qt 6\.12 · Completed** — [Release candidate](#release-candidate). Test whether the build is ready for final release and report reproducible blockers in Jira\. ID: `qt-6-12-release-candidate`. - [original plan source]() — 2026-09-08 — revision oldid=46712 — checked 2026-10-12 - [updated plan source]() — 2026-09-14 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-09-18 — revision oldid=46712 — checked 2026-10-12 - **17.** **2026-09-30 · Qt 6\.12 · Completed** — [Final release](#final-release). Review release notes and known issues; contribute follow\-up fixes for later releases\. ID: `qt-6-12-final-release`. - [original plan source]() — 2026-09-22 — revision oldid=46712 — checked 2026-10-12 - [updated plan source]() — 2026-09-30 — revision oldid=46712 — checked 2026-10-12 - [realized source]() — 2026-09-30 — revision oldid=46712 — checked 2026-10-12 - **18.** **2026-10-27 · Qt Contributors Summit 2026 · Announced** — [Qt World Summit and welcome event](#qtcs). See the edition page for the welcome program and participation details\. ID: `qtcs-2026-welcome-day`. - [announcement source]() — 2026-10-27 — revision oldid=46315 — checked 2026-10-12 - **19.** **2026-10-28 to 2026-10-29 · Qt Contributors Summit 2026 · Announced** — [Qt Contributors Summit sessions](#qtcs). Review the program and join the technical and community discussions\. ID: `qtcs-2026-sessions`. - [announcement source]() — 2026-10-28 to 2026-10-29 — revision oldid=46315 — checked 2026-10-12 - **20.** **2026-10-30 · Qt Contributors Summit 2026 · Announced** — [Hacking day](#qtcs). Check the edition page for the hacking\-day plan\. ID: `qtcs-2026-hacking-day`. - [announcement source]() — 2026-10-30 — revision oldid=46315 — checked 2026-10-12 - **21.** **2026-11-20 · Qt 6\.13 · Planned** — [Platform and module freeze](#platform-module-freeze). Review the named release’s platform and module scope; coordinate proposed exceptions with the release team\. ID: `qt-6-13-platform-module-freeze`. - [original plan source]() — 2026-11-20 — revision oldid=46325 — checked 2026-10-12 - **22.** **2026-12-04 · Qt 6\.13 · Planned** — [Feature freeze](#feature-freeze). Finish feature integration, tests, documentation, examples, and platform readiness before the deadline; check current release guidance\. ID: `qt-6-13-feature-freeze`. - [original plan source]() — 2026-12-04 — revision oldid=46325 — checked 2026-10-12 - **23.** **2026-12-07 · Qt 6\.13 · Planned** — [Branch 6\.13 from dev](#branching). Use the named stable branch for eligible fixes and continue next\-cycle feature work on dev; check release\-specific restrictions\. ID: `qt-6-13-branch-from-dev`. - [original plan source]() — 2026-12-07 — revision oldid=46325 — checked 2026-10-12 - **24.** **2026-12-18 · Qt 6\.13 · Planned** — [Beta 1](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-13-beta-1`. - [original plan source]() — 2026-12-18 — revision oldid=46325 — checked 2026-10-12 ### Dates to confirm #### Qt 6\.11 - **32.** **Qt 6\.11 · Date disputed** — [Beta 2 date disputed](#beta). Keep the schedule conflict visible until a public source resolves it\. 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](#beta). Keep the conflicting schedule date visible until a public source resolves it\. 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 These source-backed entries are outside 2026 and have no position on this year's wheel. - **25.** **Cross-year context —** **2027-01-15 · Qt 6\.13 · Planned** — [Beta 2](). Try the prerelease and report reproducible problems in Jira\. Outside 2026; shown as cross-year context. Canonical entry ID: `qt-6-13-beta-2`. - [original plan source]() — 2027-01-15 — revision oldid=46325 — checked 2026-10-12 Contribute throughout the year: [choose a small, useful change](get-started.md#choose-a-small-useful-change) · [Gerrit](https://codereview.qt-project.org/changes/) · [Jira](https://qt-project.atlassian.net/jira/) · [development mailing list](https://lists.qt-project.org/mailman/listinfo/development) · [Qt Forum, IRC and Matrix communities](https://wiki.qt.io/Online_Communities). ## 2027 **Oldest relevant source review: 2026-10-12.** | Track | Type | Pattern | | --- | --- | --- | | Qt 6\.13 | release | solid | Qt 6\.13 continued from [2026](year.md#2026). Months follow the date positions around the wheel. The complete dated list follows; entries are ordered by date, with stable IDs breaking same-day ties. - **25.** **2027-01-15 · Qt 6\.13 · Planned** — [Beta 2](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-13-beta-2`. - [original plan source]() — 2027-01-15 — revision oldid=46325 — checked 2026-10-12 - **26.** **2027-02-02 · Qt 6\.13 · Planned** — [Soft string freeze](#soft-string-freeze). Avoid changing translatable source strings; coordinate necessary exceptions with localization\. ID: `qt-6-13-soft-string-freeze`. - [original plan source]() — 2027-02-02 — revision oldid=46325 — checked 2026-10-12 - **27.** **2027-02-09 · Qt 6\.13 · Planned** — [String freeze](#string-freeze). Help translators by keeping source strings stable; follow the release’s localization workflow\. ID: `qt-6-13-string-freeze`. - [original plan source]() — 2027-02-09 — revision oldid=46325 — checked 2026-10-12 - **28.** **2027-02-12 · Qt 6\.13 · Planned** — [Beta 3](#beta). Try the prerelease and report reproducible problems in Jira\. ID: `qt-6-13-beta-3`. - [original plan source]() — 2027-02-12 — revision oldid=46325 — checked 2026-10-12 - **29.** **2027-02-18 · Qt 6\.13 · Planned** — [Branch 6\.13\.0 from 6\.13](#branching). Use the named stable branch for eligible fixes and continue next\-cycle feature work on dev; check release\-specific restrictions\. ID: `qt-6-13-branch-6-13-0`. - [original plan source]() — 2027-02-18 — revision oldid=46325 — checked 2026-10-12 - **30.** **2027-02-26 · Qt 6\.13 · Planned** — [Release candidate](#release-candidate). Test whether the build is ready for final release and report reproducible blockers in Jira\. ID: `qt-6-13-release-candidate`. - [original plan source]() — 2027-02-26 — revision oldid=46325 — checked 2026-10-12 - **31.** **2027-03-17 · Qt 6\.13 · Planned** — [Final release](#final-release). Prepare to review release notes and known issues, then contribute follow\-up fixes when the release is available\. ID: `qt-6-13-final-release`. - [original plan source]() — 2027-03-17 — revision oldid=46325 — checked 2026-10-12 ### Cross-year context These source-backed entries are outside 2027 and have no position on this year's wheel. - **24.** **Cross-year context —** **2026-12-18 · Qt 6\.13 · Planned** — [Beta 1](). Try the prerelease and report reproducible problems in Jira\. Outside 2027; shown as cross-year context. Canonical entry ID: `qt-6-13-beta-1`. - [original plan source]() — 2026-12-18 — revision oldid=46325 — checked 2026-10-12 Contribute throughout the year: [choose a small, useful change](get-started.md#choose-a-small-useful-change) · [Gerrit](https://codereview.qt-project.org/changes/) · [Jira](https://qt-project.atlassian.net/jira/) · [development mailing list](https://lists.qt-project.org/mailman/listinfo/development) · [Qt Forum, IRC and Matrix communities](https://wiki.qt.io/Online_Communities). Qt development continues throughout the year. Qt's release documentation describes [two minor releases a year](https://doc.qt.io/qt-6/qt-releases.html#release-schedules) 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](https://wiki.qt.io/Qt_6.11_Release), [6.12](https://wiki.qt.io/Qt_6.12_Release), and [6.13](https://wiki.qt.io/Qt_6.13_Release) release series across 2026 and 2027, plus the announced [2026 Qt Contributors Summit](https://wiki.qt.io/Qt_Contributors_Summit_2026). 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](get-started.md#choose-a-small-useful-change). The [Qt issue tracker](https://qt-project.atlassian.net/jira/) is the place to report a reproducible problem. For help, use the [Qt Forum](https://forum.qt.io/) or the [development mailing list](https://lists.qt-project.org/mailman/listinfo/development). ## Platform module freeze The [Qt 6.13 release schedule](https://wiki.qt.io/Qt_6.13_Release) 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](https://wiki.qt.io/Qt_Feature_Freeze) 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)](https://contribute.qt-project.org/quips/16) describes Qt framework branches. For example, the [Qt 6.13 schedule lists a planned branch from dev named 6.13 for December 7, 2026](https://wiki.qt.io/Qt_6.13_Release). 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](get-started.md#choose-a-small-useful-change) to record a clear reproduction. Report a reproducible problem in [Qt Jira](https://qt-project.atlassian.net/jira/). The [Qt 6.12 beta announcement](https://www.qt.io/blog/qt-6.12-beta-1-released) 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](https://wiki.qt.io/Qt_Localization). For example, the [Qt 6.12 soft string-freeze notice](https://lists.qt-project.org/pipermail/localization/2026-August/000644.html) asks for string stability. ## String freeze At string freeze, translators can work against more stable source text. The [Qt translation workflow](https://wiki.qt.io/Qt_Localization) has its own forward-merging branch model. For example, the [Qt 6.12 string-freeze notice](https://lists.qt-project.org/pipermail/localization/2026-August/000645.html) 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](https://qt-project.atlassian.net/jira/) for issues. For example, the [Qt 6.12 RC announcement](https://lists.qt-project.org/pipermail/announce/2026-September/000651.html) 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](https://qt-project.atlassian.net/jira/). For example, the [Qt 6.12 release announcement](https://lists.qt-project.org/pipermail/announce/2026-September/000655.html) 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](https://wiki.qt.io/Qt_Contributors_Summit_2026), 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](goals.md): 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. --- A Qt community project, built with Qt and QDoc ## Qt community destinations [Discuss development](https://lists.qt-project.org/mailman/listinfo/development) · [Ask on Qt Forum](https://forum.qt.io/) · [Review changes in Gerrit](https://codereview.qt-project.org/) · [Browse issues in Jira](https://qt-project.atlassian.net/) · [Read the Qt Wiki](https://wiki.qt.io/) · [Read Qt documentation](https://doc.qt.io/) ### Publication tools [Read the method](methodology.md) · [Publication manifest](../data/snapshots/6569b73d1aca6e4f521a0a89d707b386dbff92935491f05b82adf360d22f65ce.json) · [Report a problem](methodology.md#about-qt-town-and-corrections) · [Community conduct and safety](governance.md#community-conduct) · [Interactive website](https://qt.town/)