MIRTeam
Differences between revisions 9 and 64 (spanning 55 versions)
|
Size: 3396
Comment:
|
← Revision 64 as of 2020-03-24 15:53:06 ⇥
Size: 32
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| == Introduction == The Ubuntu MIR Team reviews packages for promotion from universe to main. See MainInclusionProcess for information on how to request an MIR. == Reviewing == The primary decision a reviewer is making is '''"Will this package be well maintained in main?"''' The following guidelines are just ways to help you answer to that question. === Security === Determine if the package may have security implications (has a history of CVEs, runs a daemon as root, parses data formats, opens a port). Err on the side of caution. If the package is security sensitive, you have two options. You can either review as much as you can and then assign to the ubuntu-security team. Or you can immediately re-assign to a member of the MIR Team that is also on the Security Team (there is usually at least one). === Common blockers === * Does it FTBFS currently? * Does it have a test suite? Make sure it's being run and will fail the build upon error. * If it's a Python package, does it use dh_python3? * If it's a Python package going on the desktop CD, will it pull in Python 2? === Packaging red flags === * Does Ubuntu carry a delta? * If it's a library, does it either have a symbols file or use an empty argument to dh_makeshlibs -V? (pass such a patch on to Debian, but don't block on it) * Does it have a bug subscriber in Ubuntu? Ideally some team in Ubuntu is looking after the package. * Does it have a watch file? * Is its update history slow or sporadic? * Is the current release packaged? * Will entering main make it harder for the people currently keeping it up to date? (i.e. are they only MOTUs?) * Lintian warnings * Is debian/rules a mess? Ideally it uses dh7 and overrides to make it as tiny as possible. === Upstream red flags === * Errors/warnings during the build * Incautious use of malloc/sprintf * Uses of sudo, gksu, pkexec, or LD_LIBRARY_PATH * Important bugs (crashers, etc) in Debian or Ubuntu == Tools == * `check-mir` can be run from a checked out source and tell you which dependencies are in universe. * `seeded-in-ubuntu PACKAGE` can tell you whether and how a given PACKAGE is seeded * `reverse-depends` can tell you reverse source or binary depends, per component * The [[http://people.canonical.com/~ubuntu-archive/component-mismatches.svg|component mismatch map]] == Bug Lists == * [[https://bugs.launchpad.net/~ubuntu-mir|All MIR bugs]] * [[https://bugs.launchpad.net/~ubuntu-mir/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE|All open MIR bugs]] * [[https://bugs.launchpad.net/~ubuntu-mir/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=none|All open unclaimed MIR bugs]] ---- CategoryUbuntuTeams |
#REDIRECT MainInclusionProcess |
MIRTeam (last edited 2020-03-24 15:53:06 by paelzer)