Reporting Bugs¶
Overview¶
The LibTIFF project uses GitLab issues to report and manage bugs and feature requests.
Please let us know when you find a problem or fix a bug.
Previously, the project used MapTools.org bugzilla to track bugs. All remaining tickets in that bugzilla instance were migrated to GitLab issues, and this system should no longer be used. All bugs filed in a older bugzilla at 'RemoteSensing.org (bugzilla.remotesensing.org)' (pre-April 2008) have unfortunately been lost.
Reporting a bug¶
If you think you've discovered a bug, please first check to see if it is already known by looking at the list of already reported bugs. Please verify that the problem is still reproducible with the current development software from GitLab. If you are capable of developing a solution for the bug, please include a proposed improvement via a subsequent merge request. Bug reports with an associated merge request are resolved most quickly.
If you'd like to enter a new bug report, you can create a new GitLab issue
Of course, reporting bugs is no substitute for discussion. Please see the Mailing List page for further details.
Reporting a security issue¶
If a bug represents a dire security issue that should not be immediately disclosed, then you may report the bug as described above, but select the checkbox which is described as "Turn on confidentiality: Limit visibility to project members with at least the Planner role". This option should be used sparingly given that it reduces the number of volunteers available to help with addressing the bug, and prevents others from seeing that the issue has already been reported. We reserve the right to de-select this checkbox and make the bug report visible to all.
The libtiff project is primarily maintained by volunteers. Given this, please to not expect us to participate in arbitrary "disclosure" timelines. Disclosure occurs when the fix is submitted to the source code repository.