Repository navigation
Feature Development
QQQ 4.0 release. Final
4.0.0is available. See QQQ 4.0 for release scope and migration guidance.
Start with a concrete issue and a bounded use case. Inspect the relevant source interfaces and existing tests before changing behavior. Discuss breaking APIs, new modules, and cross-repository contracts with maintainers and record the decision in the issue or ADR.
Create a feature branch from the intended target. Normal development targets develop; current 4.0 stabilization uses release/4.0.x. Keep the implementation within the accepted release scope. Match the module's source patterns and test both the desired behavior and relevant failure cases.
Use Public API Overview for source-based references and Testing for checks. Update application examples, migration guidance, and affected docs when behavior changes. Submit a signed conventional commit and a PR with the concrete result and validation evidence. Satisfy required CI and reviews before merge.
Design proposals and roadmap entries do not establish released capabilities. See Decision Logs, Multi-Repo Workflow, and Release Flow.
QQQ — Java metadata and application behavior.
4.0 release status · GitHub · Documentation · License materials