Qt Feature Freeze: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 1: Line 1:
=Feature Freeze=
[[Category:Release]]
 
= 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 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)
* All new features/modules targeted to coming Qt 5.x release must be added in Qt 5.x new features <s>page (wiki.qt.io/New-Features-in-Qt-5.x)<br />'''''' Reference platforms must be visible there as well<br />* All new features/modules targeted to coming Qt 5.x release must fulfill criteria for new features/modules:<br />'''''' Compiles on all reference platforms (If a module/feature is only for one platform, make sure qmake/make does nothing on the other platforms)<br />'''''' 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<br />'''''' Have documentation. No undocumented public API. Basic docs have to be there, only polishing should still be required after the freeze<br />'''''' Have examples. Have some examples showing how to use the API. Examples need to be linked to from documentation.
** Reference platforms must be visible there as well
<br />* In addition, new modules need to<br />'''''' Have a CI system<br /></s> 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<code>digia.com) as early as possible.
* 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 <span class="caps">API</span>. 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 <span class="caps">API</span>. Examples need to be linked to from documentation.
 
* In addition, new modules need to
** Have a CI system<br /> - 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.
** Each new module needs to be a part of qt5.git already in ‘dev’ branch. Please notify release team(qt-releases@digia.com) about any new module as soon as possible! Automated builds &amp; packaging needs to be OK before feature freeze date and it is maintainers responsibility to handle that with releasing team early enough!
 
===Categories:===
 
* [[:Category:Release|Release]]

Revision as of 10:44, 24 February 2015


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-cidigia.com) as early as possible.

Retrieved from "https://wiki.qt.io/index.php?title=Qt_Feature_Freeze&oldid=4940"