MainInclusionProcess

Differences between revisions 1 and 20 (spanning 19 versions)
⇤ ← Revision 1 as of 2007-01-26 10:53:02 →
Size: 1555
Editor: scandic759
Comment: create
← Revision 20 as of 2009-08-10 09:09:51 → ⇥
Size: 2664
Editor: 82-69-40-219
Comment: needs info -> incomplete, nowadays
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 1. Write a report showing that the package meets the UbuntuMainInclusionRequirements and add it here. You should use the MainInclusionReportTemplate template for the report.
 1. Add this report to the UbuntuMainInclusionQueue.
 1. Add the package to a seed, or as a (build-)dependency of a package in `main`. The package will not be moved to main automatically, but will show up in the output of [http://people.ubuntu.com/~cjwatson/anastacia.txt anastacia].
 1. Archive administrators will review the anastacia output, and for each package waiting to move into `main`, look for a corresponding report filed here
 1. If the report exists and is acceptable, the package will be moved to `main`		  1. Write a report showing that the package meets the UbuntuMainInclusionRequirements. You should use the MainInclusionReportTemplate template for the report.
 1. File a bug report for the package, and subscribe `ubuntu-mir' to it (do not assign the bug report), so that it appears in the [[https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs|bug list]]. Add the bug to the wiki page.
 1. The [[https://launchpad.net/~ubuntu-mir|MIR team]] reviews the reports, and sets acceptable ones to ''In Progress'' or ''Fix committed''. They might also delegate portions of the review to other teams, assign it to them, and set it to ''Incomplete''; common cases are getting a thorough security review from the [[https://launchpad.net/~ubuntu-security|security team]] (please see [[SecurityTeam/Auditing|SecurityTeam/Auditing]] for details on requesting an audit), or get sign-off from particular team leads about maintenance commitments.
 1. Add the package to a [[SeedManagement|seed]], or as a (build-)dependency of a package in `main`. The package will not be moved to main automatically, but will show up in the [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|component-mismatches]] list.
 1. Archive administrators will review the component-mismatches output, and for each package waiting to move into `main`, look for a corresponding [[https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs|bug]].
 1. The submitter should then take responsibility for adding the package to the seeds as per SeedManagement or adding a dependency to it.
 1. The archive administrators will promote approved packages to `main` if some other package or the seeds want it (see [[http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt|component-mismatches output]]).
Line 16: Line 18:
 * If a new source package contains only code which is already in main (e.g., the result of a source package split), it may not need a full report, but it should be listed here with a short explanation  * If a new source package contains only code which is already in main (e.g., the result of a source package split), it may not need a full report. Submitting a bug with an explanation is sufficient.

----
CategoryProcess

Packages in Ubuntu main (and restricted) are officially maintained, supported and recommended by the Ubuntu project. Security updates are provided for them as necessary by Canonical, and Canonical's standard support services apply to these packages.

Therefore, special consideration is necessary before adding new packages to these components.

  1. Hold any necessary discussion on ubuntu-devel

  2. Write a report showing that the package meets the UbuntuMainInclusionRequirements. You should use the MainInclusionReportTemplate template for the report.

  3. File a bug report for the package, and subscribe `ubuntu-mir' to it (do not assign the bug report), so that it appears in the bug list. Add the bug to the wiki page.

  4. The MIR team reviews the reports, and sets acceptable ones to In Progress or Fix committed. They might also delegate portions of the review to other teams, assign it to them, and set it to Incomplete; common cases are getting a thorough security review from the security team (please see SecurityTeam/Auditing for details on requesting an audit), or get sign-off from particular team leads about maintenance commitments.

  5. Add the package to a seed, or as a (build-)dependency of a package in main. The package will not be moved to main automatically, but will show up in the component-mismatches list.

  6. Archive administrators will review the component-mismatches output, and for each package waiting to move into main, look for a corresponding bug.

  7. The submitter should then take responsibility for adding the package to the seeds as per SeedManagement or adding a dependency to it.

  8. The archive administrators will promote approved packages to main if some other package or the seeds want it (see component-mismatches output).

Notes:

  • Reports should always be named for SOURCE packages, not binary packages
  • New binary packages from existing source packages, where the source package is already in main, do not require reports and do not need to be listed here
  • If a new source package contains only code which is already in main (e.g., the result of a source package split), it may not need a full report. Submitting a bug with an explanation is sufficient.

CategoryProcess

MainInclusionProcess (last edited 2022-10-06 04:47:43 by fitojb)