Version 31 (modified by Ademar Reis, 13 years ago) (diff)


QtWebKit-2.2 Release

QtWebKit-2.2 will be a stable release targeted at all Qt supported platforms. It was branched from trunk on 2011-05-05 (r85855). The release is planned for the end of the first half of 2011.

For a detailed list of features supported by QtWebkit-2.2 and the changes from the previous release, check the Internal Release Notes.

Status and Roadmap

Releases are made preferably on Mondays. Week numbers are from the previous week relative to when the release is made.

The current proposal (still work in progress):

Development branch and build instructions

Q&A, Trackers and Build bots

  • Developers perform weekly tests on the branch on multiple platforms;
  • TODO: Q&A team and test procedure;


Supported Platforms


Reference Platform :

  • Linux Desktop

Tier 1 :

  • Apple Mac OS X 10.6 (Cocoa)
  • Microsoft Windows XP SP3 32-bit -- needs a buildbot with tests
  • Microsoft Windows 7 32 bits -- needs a buildbot with tests
  • Symbian (Symbian^3) -- needs a buildbot with tests

Tier 2 :

  • Microsoft Windows Vista 32 bits
  • Apple Mac OS X 10.5 (Cocoa)
  • Meego 1.x

See QtWebKitPlatformSupport for the meaning of Tier 1, 2 and Reference Platform.

Release Criterias

These are the simplified, still work-in-progress release criteria. Q&A criterias and product requirements are not listed here.

Technology Previews (TPs)

A TP release is basically to invite the community to try out new features and provide some initial feedback. It has no major quality guarantees and the decision about when to release it heavily depends on the feeling from the development team.

  • All buildbots should be green;
  • The development team should be relatively confident that basic features work on the reference platform;
  • The code builds and pass through a basic smoke test on all Tier 1 platforms;


A beta release means the software is stabilizing but has known bugs we plan to fix before the release. There may be multiple betas during the development process.

  • We have buildbots running on all Tier 1 platforms and they're green;
  • The Q&A team has tested the code for regressions against the latest stable release using the same testcases (and bugs have been opened if necessary);
  • Q&A Team is actively testing the release on Tier 1 platforms and the weekly ratio between critical bugs fixed and critical bugs reported is bigger than 1;
  • The code builds and pass through a basic smoke test on all Tier 2 platforms;

Release Candidate (RC)

A RC release is made when we believe the code is ready to ship.

  • There has been at least one beta release;
  • All buildbots are green;
  • There are no critical bugs blocking the release;
  • Reports from Q&A indicate we're in better shape than the previous official version;
  • We're confident that the software is ready;

Once the first RC is out, no more "nice-to-have" fixes will be accepted and thus the meta bug is closed;

Final Release

The final release is the last RC but with final versioning.

  • One week has passed since the last RC release and no critical bugs have been reported;

Minor Update (maintenance)

  • Minor versions are released to fix security issues and may include critical bug-fixes;

See also