# Ubuntu project

> This documentation provides guidance for contributors to and maintainers of the Ubuntu Linux distribution. It covers processes and concepts, as well as project governance and team workflows. There are instructions for packaging, merging, proposed migrations, autopkgtests, and many other procedures for maintaining the Ubuntu Archive and releasing the distribution.


2026

## Pages in this subsection

- [Triaging bugs](https://documentation.ubuntu.com/project/contributors/bug-triage.md): Ubuntu receives a huge number of bug reports every day. Triaging new bugs is a
- [Bug types](https://documentation.ubuntu.com/project/contributors/bug-triage/bug-types.md): Apport reports are bugs reported via the
- [Bug status](https://documentation.ubuntu.com/project/contributors/bug-triage/bug-status.md): A report’s status is a reflection of the current development state of what is
- [Bug tags](https://documentation.ubuntu.com/project/contributors/bug-triage/bug-tags.md): Tags provide us with ways to group bugs across packages, easily find certain types of bugs, or divid...
- [Bug importance](https://documentation.ubuntu.com/project/contributors/bug-triage/bug-importance.md): Ubuntu uses the following guidelines for assigning **importance** to a bug. The
- [Bug responses](https://documentation.ubuntu.com/project/contributors/bug-triage/bug-responses.md): It is common when triaging bugs that you need to respond to the original reporter – perhaps to reque...
- [How to assign a bug to a package](https://documentation.ubuntu.com/project/contributors/bug-triage/assign-a-bug-to-a-package.md): To ensure the right people see a bug report, every report should identify the

## Optional

- [Top-level llms.txt](https://documentation.ubuntu.com/project/llms.txt): Complete documentation index.