Add new additional library: Difference between revisions
Jump to navigation
Jump to search
(Initial version) |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
There are 2 different types of additional libraries: | There are 2 different types of additional libraries: | ||
* Additional libraries which are | *Additional libraries which are following the Qt release schedule | ||
* Additional libraries which are released | *Additional libraries which are released independently (with their own release schedule) | ||
=== Additional libraries which are | ===Additional libraries which are following the Qt release schedule=== | ||
Additional libraries which are | Additional libraries which are following the Qt release schedule: | ||
* Follows Qt release | *Follows Qt release versioning | ||
* Follows Qt milestones, quality gates & release plan | *Follows Qt milestones, quality gates & release plan | ||
** Means new feature development must be ready at Qt | **Means new feature development must be ready at Qt Feature Freeze | ||
*Full CI must be in the use before FF | |||
**Means same targets with Qt release is used | |||
*Packages are tested together with the pre-releases (alpha, beta etc) | |||
=== Additional libraries which are released | ===Additional libraries which are released independently=== | ||
Additional libraries released | Additional libraries released independently: | ||
* Must have its own version numbering scheme (to clearly indicate it isn't part of any Qt release) | *Must have its own version numbering scheme (to clearly indicate it isn't part of any Qt release) | ||
* Must have its own release plan and schedule | *Must have its own release plan and schedule | ||
**Should have common pre-release milestones (FF, Alpha, Beta, RC) but in its own schedule | |||
** Should have common pre-release milestones (FF, Alpha, Beta, RC) but in its own schedule | *Release plan should be agreed with library maintainer & release team & documented in the Jira | ||
*Can't disturb Qt release | |||
== Adding new additional library | ==Adding new additional library to be available with Qt== | ||
* It is | *It is maintainer's responsibility to start discussion about adding a new additional library | ||
* Adding a new additional library starts from agreement if it will be part of Qt release or released separately (see definition above) | *Adding a new additional library starts from agreement if it will be part of Qt release or released separately (see definition above) | ||
* There should be a Jira task for every new additional library (Like QTBUG-90375) | *There should be a Jira task for every new additional library (Like QTBUG-90375) | ||
** This task should contain all needed tasks to be done | **This task should contain all needed tasks to be done | ||
* When additional library has a CI in | *When additional library has a CI in use release team can start packaging tasks | ||
** Release team must be notified about that | **Release team must be notified about that as soon as possible | ||
==More info== | |||
*https://wiki.qt.io/Qt6_Add-on_src_package_build_using_Conan_package_manager | |||
Latest revision as of 14:03, 25 January 2021
There are 2 different types of additional libraries:
- Additional libraries which are following the Qt release schedule
- Additional libraries which are released independently (with their own release schedule)
Additional libraries which are following the Qt release schedule
Additional libraries which are following the Qt release schedule:
- Follows Qt release versioning
- Follows Qt milestones, quality gates & release plan
- Means new feature development must be ready at Qt Feature Freeze
- Full CI must be in the use before FF
- Means same targets with Qt release is used
- Packages are tested together with the pre-releases (alpha, beta etc)
Additional libraries which are released independently
Additional libraries released independently:
- Must have its own version numbering scheme (to clearly indicate it isn't part of any Qt release)
- Must have its own release plan and schedule
- Should have common pre-release milestones (FF, Alpha, Beta, RC) but in its own schedule
- Release plan should be agreed with library maintainer & release team & documented in the Jira
- Can't disturb Qt release
Adding new additional library to be available with Qt
- It is maintainer's responsibility to start discussion about adding a new additional library
- Adding a new additional library starts from agreement if it will be part of Qt release or released separately (see definition above)
- There should be a Jira task for every new additional library (Like QTBUG-90375)
- This task should contain all needed tasks to be done
- When additional library has a CI in use release team can start packaging tasks
- Release team must be notified about that as soon as possible