Qt5Releasing

Contents

Qt 5 releasing gearbox

We are targeting to release new minor Qt release twice/year and some patch releases between those minor ones. Target is to release minor releases on April and October. Patch releases are done pretty much need bases: Those can be done immediately when some brown paper bag issue is found & fixed (e.g. security fix) or when there is enough critical issues fixed for next Patch release.

Most of releasing related issues are decided in virtual release team meetings. Meetings are led by release manager and everyone can join to those meetings by informing willingness to release manager. Meetings are held in irc, #qt-releases channel. To get invitation to these meetings please sent request to the release manager.

Qt 5 release phases

Patch release doesn't have official release phases; It is released when needed and when quality is good enough.

Branches & Qt versions

There is few different development branches in Qt 5: Development branch & feature branches (like 5.4, 5.3)

Development branch has content targeted to next minor release (Qt 5.x). After feature freeze of Qt 5.x code is branched from development branch to 5.x and work for that minor release continues in that new branch. Development branch is again for new minor release Qt 5.(x+1).

Feature branches (5.x) has content for next release (minor or patch). Alpha and beta releases are done from feature branch. Release branch(5.x.y) is created after (last) beta release, near release candidate phase. After branching work for release candidate & final release continues in release branch and feature branch is for next patch release.

Release branch is for finalizing the release. All final releases are done from release branch. Only really important error corrections are allowed to be integrated to release branch. Release team is approving all changes coming in to release branch.