Qt Feature Freeze

This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

Feature Freeze

• All new features/modules targeted to coming Qt 5.x release must be in ‘dev’ –branch well before feature freeze date
• All new features/modules targeted to coming Qt 5.x release must be added in Qt 5.x new features -page (wiki.qt.io/New-Features-in-Qt-5.x)

' Reference platforms must be visible there as well

• All new features/modules targeted to coming Qt 5.x release must fulfill criteria for new features/modules:

' Compiles on all reference platforms (If a module/feature is only for one platform, make sure qmake/make does nothing on the other platforms) ' Have tests. Automated tests should cover as much as possible of the new functionality. If certain areas are not covered by automated tests, Agree with Lars how testing will be done for those ' Have documentation. No undocumented public API. Basic docs have to be there, only polishing should still be required after the freeze ' Have examples. Have some examples showing how to use the API. Examples need to be linked to from documentation.

• In addition, new modules need to

' Have a CI system - New modules that are going to be part of Qt releases need to have a CI system set up well before actual feature freeze date. Contact CI team (qt-ci@digia.com) as early as possible.