• Logo
    Ubuntu project
  • documentation.ubuntu.com
  • More resources
    • Discourse
    • Matrix
    • GitHub
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Ubuntu project documentation
Ubuntu project documentation
  • How Ubuntu is made
    • Governance
      • Ethos
        • Ubuntu Code of Conduct
        • Diversity policy
        • Our Mission
      • Peers
    • Key concepts
      • Ubuntu releases
      • Upstream and downstream
      • Supported architectures
      • Launchpad
      • Package archive
      • Package format
      • Package lifecycle
      • Version string format
      • Patches
      • Phased updates
      • DEP 3 - patch file headers
      • Debian policy
      • debian/ directory
      • Filesystem hierarchy standard
    • Process overviews
      • Release cycle
      • Freezes
      • Merges & syncs
      • Sync process
      • Transitions
      • Proposed migration
      • Backports
      • Sponsorship
      • Stable Release Updates
      • Main Inclusion Review (MIR)
        • MIR roles and steps
        • Process states
        • MIR exception - font packages
        • MIR exception - OEM packages
        • MIR - re-reviews
        • MIR - Rust code in main
  • Contributors
    • Getting started
      • Setting up for Ubuntu development
      • Get the source of a package
    • Debugging
      • Debug an Apport crash
    • Fix a bug
      • Report a bug
      • Download a new upstream version
      • Extract packages
      • Install built packages
      • Fix a bug in package
      • Build packages
      • Package building
      • Propose changes
      • Bug fixing checklist
    • Patching
      • Making changes to a package
      • Patch management
      • Work with Debian patches
      • Dual maintenance with Salsa and git-ubuntu
      • Committing your changes
      • Merge proposals
    • Testing
      • How to run package tests
    • New packages
      • How to create a new package
      • Request an SRU
      • Upload packages to a PPA
    • How to find a sponsor
    • Advanced contributor tasks
      • Check publication history
      • Checking reverse dependencies
      • Merge Proposal review
      • How to merge a package
      • How to sponsor
      • +1 Maintenance
      • +1 Maintenance report template
      • Request a package removal
      • MIR bug request template
      • How to use MIR templates
    • Contribute docs
  • Maintainers
    • Uploader tasks
      • Sponsoring
      • How to update seeds
      • How to work with the upload queue
    • Handling MIR reviews
      • MIR reviewer's template
    • SRU tasks
      • How to review an SRU
    • Archive Admin tasks
      • NEW review
      • Remove a package
      • Package overrides
      • Priority mismatches
      • Signing bootloaders
      • Change phasing on delivering SRU updates
      • i386
      • Archive-related services
      • Check contributions to AA process and documentation
  • Who makes Ubuntu
    • Councils and Boards
      • Community Council
      • Conflict resolution
      • Delegation
      • Membership Board
      • Technical Board
    • Roles and responsibilities
      • About the uploaders role
        • Uploaders service level agreement
      • About the MIR role
        • MIR team weekly status meeting
        • MIR Service Level Objectives
      • About the SRU role
        • SRU service level agreement
      • Archive Administration
    • Joining a role
      • Path to upload rights
      • Membership in Package Set
      • Membership in MOTU
      • Membership in Core Developers
    • Specialist teams
      • The Bug Squad
      • Ubuntu Bug Control
  • Glossary
  • Staging/preview area
    • Archive Admin museum
    • Germinate
    • Mirror scripts
    • Mirrors
    • New packages
    • Content that doesn’t belong to AA
    • The Package Archive
    • Partner archive
    • Push mirroring
    • Seed management
    • Sponsorship process
    • Feature Freeze
    • Freeze exceptions
    • Request a Freeze exception
Back to top
Contribute to this page

Handling MIR reviews¶

As part of the Main Inclusion Review (MIR) the MIR Team reviews cases that have been submitted. To do so they use the MIR reviewer’s template alongside the general guidance on using such templates.

Furthermore they drive the MIR team weekly status meeting for coordination of efforts any related discussions.

  • MIR reviewer's template
Copyright © 2025 CC-BY-SA, Canonical Ltd.
Last updated on Jul 28, 2025
Contents
  • Handling MIR reviews