Deprecation Policy

Deprecation and migration

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

Deprecate public APIs before ordinary removal, provide an alternative, and document the intended removal release. Preserve a migration window and use a major release for incompatible removals. The actual annotation, release notes, and approved migration guide define the schedule for each API; the old wiki examples gave conflicting version timelines.

Required documentation and checks

Use Java @Deprecated and Javadoc to explain the replacement and relevant behavior changes. Update source examples, release notes, and migration guidance. Test the replacement, affected consumers, and compatibility boundaries. Do not infer a runtime warning from the annotation alone.

QQQ 4.0 is a breaking transition from 0.x. Follow the specific migration guide, including removed or tightened APIs, rather than illustrative LegacyAction or QContext.getCurrent() examples previously on this page.

Urgent security, legal, or infrastructure changes may require a separately documented exception. Record the reason, impact, alternative, and validation evidence with maintainer review. Do not silently redefine compatibility or advertise an unverified support period.

Semantic Versioning Policy · Changelog and Tagging