MainInclusionProcess

Differences between revisions 2 and 3
Revision 2 as of 2007-02-14 08:22:49
Size: 1865
Editor: 87
Comment: clarify process for approval and promotion
Revision 3 as of 2007-03-12 11:43:13
Size: 1877
Editor: chiark
Comment: archive bits moved to ~ubuntu-archive
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 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. 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/~ubuntu-archive/anastacia.txt anastacia].
Line 12: Line 12:
 1. The archive administrators will promote approved packages to `main` if some other package or the seeds want it (see [http://people.ubuntu.com/~cjwatson/anastacia.txt Anastacia output]).  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/anastacia.txt Anastacia output]).

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 and add it here. You should use the MainInclusionReportTemplate template for the report.

  3. Add this report to the UbuntuMainInclusionQueue.

  4. 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/~ubuntu-archive/anastacia.txt anastacia].

  5. Archive administrators will review the anastacia output, and for each package waiting to move into main, look for a corresponding report filed here

  6. If the report exists and is acceptable, the report will be marked 'approved'.
  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/anastacia.txt Anastacia 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, but it should be listed here with a short explanation

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