Skip to content

Guidelines for bug submission #33

@lrberge

Description

@lrberge

First thanks for the interest in the package and for wanting to submit a bug report. This feedback is invaluable since it significantly improves software quality, benefiting to all users.

Here's a few guidelines before submitting a bug:

  1. Bugs are corrected at almost every release. So ensure you have the latest version of the software running. Currently it's Version .

  2. Every time a bug is corrected, it's reported in the NEWS file. Please have a look at it to see whether it isn't already fixed in the development version.

  3. I know it's some work, but please provide a minimal working example in your report with reproducible code and data. If your bug only happens for some large data set and you're not able to make it appear for data of smaller size, you can DM me the data. A minimal working example ensures that:

    1. you really have encountered a bug and it's not a user-side mistake.
    2. it can be quickly solved.

There are many very good examples of bug reports in past issues (see #4, #10, or #17 to name a few).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions