MainInclusionProcess

Differences between revisions 9 and 10
Revision 9 as of 2007-12-04 19:20:36
Size: 2274
Editor: yttrium
Comment: spelling
Revision 10 as of 2008-01-08 11:48:36
Size: 2167
Editor: p5B0E98C6
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 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. '''Note:''' Please do not add the report to the UbuntuMainInclusionQueue, which will become obsolete soon.  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.

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 [https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs bug list]. Add the bug to the wiki page.

  4. The [https://launchpad.net/~ubuntu-mir MIR team] reviews the reports, and sets acceptable ones to Fix committed.

  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 [http://people.ubuntu.com/~ubuntu-archive/component-mismatches.txt 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 [https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs bug].

  7. The submitter should then take responsibility for adding the package to the seeds 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 [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 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.

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