MainInclusionReportMauve

Revision 1 as of 2008-07-08 05:25:37

Clear message

Main Inclusion Report for mauve

work in progress

Requirements

  1. Availability: [http://archive.ubuntu.com/ubuntu/pool/universe/s/sourcepackage]; available for all supported architectures or some subset ?

  2. Rationale:

    • Build dependency of ...
  3. Security:

  4. Quality assurance:

    • In what situations does the package not work out of the box without configuration ?
    • Does the package ask any debconf questions higher than priority 'medium' ?
    • [http://bugs.debian.org/src:SOURCE_PACKAGE_NAME Debian bugs]: (mention any that are particularly relevant, and any showstoppers)

    • [http://packages.qa.debian.org/S/SOURCE_PACKAGE_NAME.html Maintenance in Debian] is frenetic/vigorous/calm/dead ?

    • [http:// Upstream] is frenetic/vigorous/calm/dead ?

    • [http:// Upstream bug tracker]: (mention any particularly relevant or critical)

    • Hardware: Does this package deal with hardware and if so how exotic is it ?
    • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?
  5. Standards compliance:

  6. Dependencies:

    • ...
    • Are these all in main ?
  7. Background information:

    • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
    • What do upstream call this software ? Has it had different names in the past ?

Reviewers

MIR bug: [https://launchpad.net/bugs/BUGNUMBER]

The author of this report should put their name here; reviewers will add comments etc. too