Bug Process

Bug reporting and resolution

QQQ 4.0 release. Final 4.0.0 is available. See QQQ 4.0 for release scope and migration guidance.

Report a reproducible issue with the exact QQQ version and source reference, Java and Maven versions, operating environment, affected backend, steps, expected result, and actual result. Include a minimal example and relevant error context with secrets and private data removed.

Triage and resolution

Confirm the issue, classify impact, identify affected releases, and link duplicates or related repository work. Assign priority based on impact and available resources; historical response-time tables are not support commitments. Security-sensitive reports should follow the selected repository's security reporting instructions.

Implement the fix in a feature or appropriate stabilization branch, add a meaningful regression check, and run relevant quality gates. Review compatibility, update migration guidance when needed, and satisfy current PR requirements.

A bug is released only when the corrected artifact is published and verified. For the 4.0 train, changes after candidate acceptance require a new immutable candidate and renewed application acceptance. Record the final version and link the release evidence back to the issue.

Common Errors · Testing · Release Flow