Skip to content

Satisfy and declare the datex4j 1.0 readiness gate #40

Description

@juherr

Goal

Release 1.0 only after the SDK demonstrates sustained API stability, interoperability, security, and useful domain coverage.

Acceptance criteria

  • The public API passes multiple release cycles without unplanned breakage.
  • Java 21 and Java 25 builds are blocking.
  • Security, dependency isolation, compatibility, and consumer tests are blocking.
  • XML covers every advertised version from 2.0 through 2.3 and 3.0 through 3.7.
  • Official-feed compatibility and motivated exceptions are public.
  • Traffic, parking, SRTI, and AFIR provide useful business APIs.
  • AFIR static, dynamic, OCPI, profile validation, and delta flows pass end to end.
  • Release automation, signatures, SBOM, changelog, and migration guidance are operational.
  • Performance regressions above 15 percent are explained.
  • No generated model source has been modified manually.

Dependencies

This is the final convergence issue and depends on the completion or explicit disposition of all earlier milestones.

Planning

  • Priority: P1
  • Complexity: L

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:apiPublic API design and compatibilityarea:releasePublishing, release engineering, and supply chainarea:testingTest infrastructure, fixtures, and compatibility corpuscomplexity:LLarge cross-component changeenhancementNew feature or requestpriority:P1Release-blocking or highest-value work

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions