# Quality and feedback Quality is a consistent benchmark with all upgrades no matter how big or small. To ensure we release and maintain secure and stable nodes and upgrades, we encourage the community to help with testing and providing feedback. This is especially important in the lead up to a major event, like a protocol version change (or hard fork). We always actively encourage issues or bugs to be raised by our members, and the community more broadly towards those teams who are supporting the continuity of Cardano. To raise a ticket, simply log an appropriate ticket on GitHub under the 'cardano-node' repository at the following link: A number of options are available, and select what you believe a best fit. All tickets will be triaged by a member of the joint technical teams and assigned a severity.

Example of Issue and Bug tickets available

Soon we hope to provide analytics, to track a wealth of health information associated with the repositories. As well as history and volume trending of issues and bugs, by a number of measures. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.intersectmbo.org/intersect-knowledge-base/cardano-facilitation-services/cardano-development/cardano-hardforks-and-upgrades/quality-and-feedback.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.