Qt Creator Releases: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(133 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Category:Tools::QtCreator]]


===Qt Creator Release Cycle===
===Upcoming Releases===


We aim for 3 Qt Creator minor releases each year. Each minor release goes through the following stages before the final release date:
Tentative dates:


* T-8 Weeks: Feature freeze
Qt Creator 16.0.1: ~Apr 10 2025
* T-6 Weeks: Beta release + soft string freeze
* T-4 Weeks: String freeze
* T-2 Weeks: Release candidate
* T-0 Weeks: Final release


These times are approximate and can vary a bit, depending on the state of Qt Creator during the process.
Qt Creator 17


Patch releases can happen after the final release, mostly with the scope of fixing brown paper bag and high priority issues (see also the [[Submit-Policies|Qt Creator Submit Policies]] ''[qt.io]''). We do not maintain multiple Qt Creator minor releases in parallel, usually there is no patch release after the beta of the next minor release has been released. Qt Creator’s schedule is not aligned with Qt’s schedule, but we typically provide a patch release exactly matching Qt releases which is then released at the same time.
* Feature freeze wk17 (~Apr 24 2025)
* Beta release wk19 (~May 8 2025)
* String freeze wk21 (~May 22 2025)
* RC release wk23 (~Jun 5 2025)
* Final release wk25 (~Jun 18 2025)


The schedule for the next minor is typically set around release time, starting with a period about two months which focuses on feature development for the upcoming release. (During that time there might be patch releases as described above.)
Qt Creator 18


===Upcoming Releases===
* Feature freeze wk36 (~Sep 4 2025)
* Beta release wk38 (~Sep 18 2025)
* String freeze wk40 (~Oct 2 2025)
* RC release wk42 (~Oct 16 2025)
* Final release wk44 (~Oct 30 2025)


Tentative dates:
The mentioned dates are typically Thursdays of the weeks, packages are meant to be ready by Tuesday. Actual release then typically happens on Wednesday or Thursday.


Qt Creator 4.0:
A collection of older release plans is found at [[Old Qt Creator Releases]].


* Feature freeze w10 (~Mar 1 2016)
===Qt Creator Release Cycle===
* Beta release w12 (~Mar 23 2016)
* String freeze w14 (~Apr 5 2016)
* Release candidate w16 (~Apr 19 2016)
* Final release w18 (~May 3 2016)


Qt Creator 4.1:
We aim for 3 Qt Creator major releases each year. Each release goes through the following stages before the final release date:


* Feature freeze w26 (~Jun 21 2016)
* T-8 Weeks: Feature freeze
* Beta release w28 (~Jul 5 2016)
* T-6 Weeks: Beta release + soft string freeze
* String freeze w30 (~Jul 19 2016)
* T-4 Weeks: String freeze
* Release candidate w32 (~Aug 2 2016)
* T-2 Weeks: Release candidate
* Final release w34 (~Aug 16 2016)
* T-0 Weeks: Final release


Qt Creator 4.2:
These times are approximate and can vary a bit, depending on the state of Qt Creator during the process.
 
* Feature freeze w44 (~Oct 11 2016)
* Beta release w46 (~Oct 25 2016)
* String freeze w48 (~Nov 8 2016)
* Release candidate w50 (~Nov 22 2016)
* Final release w50 (~Dec 6 2016)
 
The mentioned dates are typically Tuesdays of the weeks, packages are meant to be ready by then. Actual release typically happens on Wednesday or Thursday.
 
A collection of older release plans is found at [[Old Qt Creator Releases]].


===Categories:===
Patch releases can happen after the final major release, mostly with the scope of fixing embarrassing bugs and high priority issues (see also the [[Submit-Policies|Qt Creator Submit Policies]] ''[qt.io]''). We do not maintain multiple Qt Creator major releases in parallel, usually there is no patch release after the beta of the next release has been released. Qt Creator’s schedule is not aligned with Qt’s schedule, but we typically provide a patch release exactly matching Qt releases which is then released at the same time.


* [[:Category:Tools|Tools]]
The time after a final (.0) release starts with a period of about two months (52 weeks / 3 releases - 8 weeks from feature freeze to final = 9 1/3 weeks) which focuses on feature development for the upcoming release. (During that time there might be patch releases as described above.)
** [[:Category:Tools::QtCreator|QtCreator]]

Revision as of 08:10, 2 April 2025


Upcoming Releases

Tentative dates:

Qt Creator 16.0.1: ~Apr 10 2025

Qt Creator 17

  • Feature freeze wk17 (~Apr 24 2025)
  • Beta release wk19 (~May 8 2025)
  • String freeze wk21 (~May 22 2025)
  • RC release wk23 (~Jun 5 2025)
  • Final release wk25 (~Jun 18 2025)

Qt Creator 18

  • Feature freeze wk36 (~Sep 4 2025)
  • Beta release wk38 (~Sep 18 2025)
  • String freeze wk40 (~Oct 2 2025)
  • RC release wk42 (~Oct 16 2025)
  • Final release wk44 (~Oct 30 2025)

The mentioned dates are typically Thursdays of the weeks, packages are meant to be ready by Tuesday. Actual release then typically happens on Wednesday or Thursday.

A collection of older release plans is found at Old Qt Creator Releases.

Qt Creator Release Cycle

We aim for 3 Qt Creator major releases each year. Each release goes through the following stages before the final release date:

  • T-8 Weeks: Feature freeze
  • T-6 Weeks: Beta release + soft string freeze
  • T-4 Weeks: String freeze
  • T-2 Weeks: Release candidate
  • T-0 Weeks: Final release

These times are approximate and can vary a bit, depending on the state of Qt Creator during the process.

Patch releases can happen after the final major release, mostly with the scope of fixing embarrassing bugs and high priority issues (see also the Qt Creator Submit Policies [qt.io]). We do not maintain multiple Qt Creator major releases in parallel, usually there is no patch release after the beta of the next release has been released. Qt Creator’s schedule is not aligned with Qt’s schedule, but we typically provide a patch release exactly matching Qt releases which is then released at the same time.

The time after a final (.0) release starts with a period of about two months (52 weeks / 3 releases - 8 weeks from feature freeze to final = 9 1/3 weeks) which focuses on feature development for the upcoming release. (During that time there might be patch releases as described above.)