Bug Report writing Guidelines - deegree/deegree3 Wiki

Bug Report writing Guidelines

Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.

But keep in mind: The github issue tracker is NOT a support forum! You must not report questions or support inquires! We will close all issues of this kind without further explanations!

Before reporting a bug please make every effort to resolve the problem yourself! Upgrade to the most recent version of deegree (Download from www.deegree.org/download). If the issue remains, then check the Open Bugs Report if a similar issue has been reported. Tip: You can vote on an issue using GitHub reactions!

If the issue persists and has not been reported by other users we encourage you to submit a bug report here https://github.com/deegree/deegree3/issues/new. Please add all information available. See our checklist for more information.

Checklist

General Principles

Reporting a security vulnerability

If you encounter a security vulnerability in deegree please take care to report the issue in a responsible fashion:

see also our security policy.

Ticket lifecycle