Qt Feature Freeze: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Generalized Qt 5) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Release]] | [[Category:Release]] | ||
All new features/modules targeting an upcoming Qt | All new features/modules targeting an upcoming major or minor Qt release must: | ||
* Be merged into the 'dev' git branch well before feature freeze date. | * Be merged into the 'dev' git branch well before feature freeze date. | ||
* Be added to a Wiki page that list all new features (for example, [[New Features in Qt 5.5]]). | * Be added to a Wiki page that list all new features (for example, [[New Features in Qt 5.5]]). | ||
** Note: The Wiki page must list reference platforms too. | ** Note: The Wiki page must list reference platforms too. | ||
** Add the Wiki page to [[:Category:Release]] and [[:Category:Developing with Qt::Qt 5]] (adapting for version if needed). | |||
* Fulfill criteria for new features/modules: | * 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.) | ** Compiles on all reference platforms. (If a module/feature is only for one platform, make sure qmake/make does nothing on the other platforms.) | ||
Latest revision as of 08:14, 17 June 2020
All new features/modules targeting an upcoming major or minor Qt release must:
- Be merged into the 'dev' git branch well before feature freeze date.
- Be added to a Wiki page that list all new features (for example, New Features in Qt 5.5).
- Note: The Wiki page must list reference platforms too.
- Add the Wiki page to Category:Release and Category:Developing with Qt::Qt 5 (adapting for version if needed).
- 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 the Chief Maintainer on how to test those.
- Have documentation. No undocumented public API. Basic docs have to be there, only polishing should still be required after the feature freeze.
- Have examples. Have some examples showing how to use the API. Examples need to be linked to from documentation.
In addition, new modules must have a CI system well before actual feature freeze date. Contact CI team (qt.ci@qt.io) as early as possible.