GLIBC Bugzilla Bug Triage
We're looking for volunteers to help with the GLIBC Bugzilla bug triage initiative. The following is the list of a triage participant's duties:
- Deal with new bug reports in a timely manner.
Identify duplicate bugs reports. Close duplicate reports as dupe. Duplicates will show up on the GLIBC duplicate bugs page.
- Verify bug validity, which involves the following:
- Verify the validity of the test-case (identify user error).
- Verify the behavior against the existing documentation (info page and man page).
- Verify the bug premise against applicable standards (i.e. C11, POSIX, ieee754, ieee754r, ieee854).
- Ask for clarification of standards and documentation from developers.
- Make sure the bug still occurs with latest git glibc (especially applicable when reviewing old bugs).
- Say in the bug what you have verified, for the benefit of future readers.
Narrow the breadth of the bug's scope if applicable.
Set bug fields in accordance with bugzilla/procedures. In particular, ensure ASSIGNED and SUSPENDED states are used correctly, remove default assignees and ping the bug if someone assigned it to themself a long time ago but doesn't appear to have been working on it. Make sure the bug is in the most appropriate component ("libc", "ports", "nptl", "manual" etc.).
- Implement a minimal test-case from a user submitted test-case or create one if a test-case is lacking.
- Create a test-case that can be injected into the GLIBC test-skeleton.c framework.
- If the bug report includes a patch (or links to one previously posted on a mailing list) from someone covered by a current FSF copyright assignment, or too small to need an assignment, then try to review the patch, ask the submitter to post it to libc-alpha for a wider audience to review it, or ask the submitter to update it for current sources and repost it, as appropriate.
- Consider fixing the bug yourself if straightforward, or pester developers if appropriate via posting to libc-alpha.
- Once fixes are delivered verify that problem is fixed.
- Prepare fixes to man pages or info pages as necessary.
- Review old bugs in the same way from time to time.
If you can't do all those things for a bug, any subset of them is still useful.
Further reading of Roland McGrath's comments regarding GLIBC bug triage can be found here.
- Don't be intimidated by the process. We appreciate contribution and the process can be refined as we go along.
The bugzilla bug entry 'owner' field is an indication of the triage participant who is looking at the entry. If you're comfortable addressing the problem please assign yourself as the owner. Please remember to unassign yourself if no longer working on a bug.
- In the course of your bugzilla triage work you may identify two separate bugs. If you find the need to open a new bug entry follow the guidelines below.
If you have questions on the process please contact email@example.com.
Guidelines for Bugzilla Fields
See bugzilla/procedures for what settings of various fields in bugs mean.
Guidelines for New Features
New feature patches that don't get reviewed reasonably quickly should have bugzilla entries created for them; the same applies to other unreviewed patches that do not add new features. This is done so that patches don't get lost and so the release manager is able to find all patches when it comes time to spin a release.
Submitting a Bug Report
If you would like to submit a bug report against GLIBC please read the GNU Guidelines for filing a GLIBC bug.
Before you file, take a look at the GLIBC duplicate bugs page to see if you're filing something that's already been identified. Also do a query in bugzilla before you file.
- No man pages are part of glibc, DO NOT REPORT MAN PAGE BUGS HERE! There is a separate GLIBC man page project.
Contact Michael Kerrisk <firstname.lastname@example.org> for man pages listed on http://www.kernel.org/doc/man-pages/online_pages.html.
The Sourceware Bugzilla hosts GLIBC bugs under the glibc product.