MainInclusionProcess

Differences between revisions 23 and 24
Revision 23 as of 2010-01-04 16:36:34
Size: 0
Editor: pD9EB73D3
Comment: will be replaced with /Proposed
Revision 24 as of 2010-01-04 16:39:25
Size: 2919
Editor: pD9EB73D3
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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. Thoroughly go through UbuntuMainInclusionRequirements, check that the package meets all the points there. Write down issues that violate the requirements. If this package has nontrivial problems, it is not eligible for main inclusion, and needs to be fixed first.
 1. File a bug report for the package, titled "[MIR] sourcepackagename". Include the rationale and description of the violations of UbuntuMainInclusionRequirements, and a confirmation that you checked the requirements carefully.
 1. Subscribe `ubuntu-mir` to the bug report (do not assign it to anyone), so that it appears in the [[https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs|MIR bug list]].
 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]]).

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.
 * If a new source package contains only code which is already in main (e.g., the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. 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. Thoroughly go through UbuntuMainInclusionRequirements, check that the package meets all the points there. Write down issues that violate the requirements. If this package has nontrivial problems, it is not eligible for main inclusion, and needs to be fixed first.

  2. File a bug report for the package, titled "[MIR] sourcepackagename". Include the rationale and description of the violations of UbuntuMainInclusionRequirements, and a confirmation that you checked the requirements carefully.

  3. Subscribe ubuntu-mir to the bug report (do not assign it to anyone), so that it appears in the MIR bug list.

  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.
  • If a new source package contains only code which is already in main (e.g., the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a bug with an explanation is sufficient.


CategoryProcess

MainInclusionProcess (last edited 2020-09-22 06:41:03 by paelzer)