Add new additional library: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Created page with "Category:Release")
 
(Initial version)
Line 1: Line 1:
[[Category:Release]]
[[Category:Release]]
There are 2 different types of additional libraries:
* Additional libraries which are released with Qt release
* Additional libraries which are released separately
=== Additional libraries which are delivered with Qt release ===
Additional libraries which are delivered with Qt release
* Follows Qt release numbering
* Follows Qt milestones, quality gates & release plan
** Means new feature development must be ready at Qt FF
** Full CI must be in the use before FF
*** Means same targets with Qt release is used
** Packages are in pre-releases (alpha, beta etc)
=== Additional libraries which are released separately ===
Additional libraries released separately
* 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
** Can't disturb Qt release
** 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
== Adding new additional library in Qt ==
* It is maintainers 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 the use release team can start packaging it
** Release team must be notified about that early enough

Revision as of 07:27, 19 January 2021

There are 2 different types of additional libraries:

  • Additional libraries which are released with Qt release
  • Additional libraries which are released separately

Additional libraries which are delivered with Qt release

Additional libraries which are delivered with Qt release

  • Follows Qt release numbering
  • Follows Qt milestones, quality gates & release plan
    • Means new feature development must be ready at Qt FF
    • Full CI must be in the use before FF
      • Means same targets with Qt release is used
    • Packages are in pre-releases (alpha, beta etc)

Additional libraries which are released separately

Additional libraries released separately

  • 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
    • Can't disturb Qt release
    • 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

Adding new additional library in Qt

  • It is maintainers 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 the use release team can start packaging it
    • Release team must be notified about that early enough