(find-maint.info)Bugs

---

Next: Distributions Prev: Testing Up: Top

---

Enter node , (file) or (file)node

9 Bugs
******

Bugs are logged in the Savannah bug tracker
<https://savannah.gnu.org/bugs/?group=findutils>.  The tracker offers
several fields but their use is largely obvious.  The life-cycle of a
bug is like this:

Open
     Someone, usually a maintainer, a distribution maintainer or a user,
     creates a bug by filling in the form.  They fill in field values as
     they see fit.  This will generate an email to
     <bug-findutils@gnu.org>.

Triage
     The bug hangs around with 'Status=None' until someone begins to
     work on it.  At that point they set the "Assigned To" field and
     will sometimes set the status to 'In Progress', especially if the
     bug will take a while to fix.

Non-bugs
     Quite a lot of reports are not actually bugs; for these the usual
     procedure is to explain why the problem is not a bug, set the
     status to 'Invalid' and close the bug.  Make sure you set the
     'Assigned to' field to yourself before closing the bug.

Fixing
     When you commit a bug fix into git (or in the case of a contributed
     patch, commit the change), mark the bug as 'Fixed'.  Make sure you
     include a new test case where this is relevant.  If you can figure
     out which releases are affected, please also set the 'Release'
     field to the earliest release which is affected by the bug.
     Indicate which source branch the fix is included in (for example,
     4.2.x or 4.3.x).  Don't close the bug yet.

Release
     When a release is made which includes the bug fix, make sure the
     bug is listed in the NEWS file.  Once the release is made, fill in
     the 'Fixed Release' field and close the bug.