Differences between revisions 5 and 6
Revision 5 as of 2008-03-26 22:59:03
Size: 3262
Editor: Sean Curry
Comment: fixed typo
Revision 6 as of 2008-04-09 21:32:00
Size: 3943
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:

=== Guidelines for Bugs ===
Line 32: Line 34:
Every once in a while Ulrich will make a statement about what severity and priority is allowed for a particular type of bugs. We need to find and document those guidelines.  * Every once in a while Ulrich will make a statement about what severity and priority is allowed for a particular type of bugs. We need to find and document those guidelines.
}}}

=== Guidelines for New Features ===
New feature patches should have bugzilla entries created for them. 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.
{{{#!wiki blue/solid
 * New features bugzilla entries should have the '''severity''' marked '''enhancement'''. Don't mess with the priority, i.e. leave it the default. Setting the priority to '''critical''' is a guaranteed way to get your bugzilla ignored.
 * Once a bugzilla entry is created a mailing list post to libc-alpha should be made directing the developers to look at the bugzilla.

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:

  1. Deal with new bug reports in a timely manner.
  2. Identify duplicate bugs reports. Close duplicate reports as dupe. Duplicates will show up on the GLIBC duplicate bugs page.

  3. 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. C99, POSIX, ieee754, ieee754r, ieee854).
    • Ask for clarification of standards and documentation from developers.
  4. Narrow the breadth of the bug's scope if applicable.

  5. Implement a minimal test-case from a user submitted test-case or create one if a test-case is lacking.
  6. Create a test-case that can be injected into the GLIBC test-skeleton.c framework.
  7. Pester developers via posting to libc-alpha.
  8. Once fixes are delivered verify that problem is fixed.
  9. Prepare fixes to man pages or info pages as necessary.

Further reading of Roland McGrath's comments regarding GLIBC bug triage can be found here.

Participation Steps

  1. Don't be intimidated by the process. We appreciate contribution and the process can be refined as we go along.
  2. 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.

  3. 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.
  4. If you have questions on the process please contact <rsa at us dot ibm dot com>.

Guidelines for Bugzilla Severity and Priority

Bugzilla severity and priority guidelines:

Guidelines for Bugs

  • Every once in a while Ulrich will make a statement about what severity and priority is allowed for a particular type of bugs. We need to find and document those guidelines.

Guidelines for New Features

New feature patches should have bugzilla entries created for them. 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.

  • New features bugzilla entries should have the severity marked enhancement. Don't mess with the priority, i.e. leave it the default. Setting the priority to critical is a guaranteed way to get your bugzilla ignored.

  • Once a bugzilla entry is created a mailing list post to libc-alpha should be made directing the developers to look at the bugzilla.

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.

  1. Do not report build errors in bugzilla! Take it to #glibc on freenode or to the libc-help mailing list. If you've identified an actual problem with a Makefile you can bring that to libc-alpha directly.
  2. No man pages are part of glibc, DO NOT REPORT MAN PAGE BUGS HERE! There is a separate GLIBC man page project. Todo: identify

The Sourceware Bugzilla hosts GLIBC bugs under the glibc product.

None: Bug_Triage (last edited 2016-11-26 04:44:16 by CarlosODonell)