The page BugTriage contains general bug triage tips, but many of them are outdated or even wrong, so here is a summary that is fresh and applies perfectly for MariaDB packaging in Debian.
== Bug overview
To see a list of all MariaDB bugs from all the source packages use the page https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mariadb-10.5;src=mariadb-10.4;src=mariadb-10.3;src=mariadb-10.2;src=mariadb-10.1;src=mariadb-10.0;src=mariadb-5.5
== Submitting bugs
=== FTBFS bugs
When submitting bugs about MariaDB failing to build from sources (FTBFS) there usually needs to be more elaborate metadata. Example:
Subject:
mariadb-10.3: FTBFS on alpha: relocation truncated to fit
Start of body:
Source: mariadb-10.3 Version: 1:10.3.13-1 Severity: serious Justification: fails to build from source User: debian-alpha@lists.debian.org Usertags: alpha ftbfs
== Responding to bugs
Simply reply to the bug, but remember to put control stanzas in the beginning of the email. Examples
Control: tags -1 wontfix Control: severity -1 wishlist Control: forwarded -1 https://jira.mariadb.org/browse/MDEV-14900 Control: merge -1 123456 Control: retitle -1 Proper title for this bug
For full list of commands see https://www.debian.org/Bugs/server-control For full list of the argument options that can be given to commands see https://www.debian.org/Bugs/Developer#severities and https://www.debian.org/Bugs/Developer#tags
== Closing bugs
There are two ways:
1. Include a "(Closes: #123456)" in the debian/changelogs entry. This will automatically mark the bug fixed at the version uploaded and at the time of upload. 2. Send email to the bug with "Version: 1:10.5.5-1" as the first line to indicate what version the bug was fixed in.