Skip to content

Qualify all seven stable libraries against the ecosystem standard #1

Description

@stefan-jansen

Objective

Qualify data, engineer, backtest, specs, live, diagnostic, and models against the shared stable-release standard, remediate every actionable deviation, and retain a dated evidence snapshot.

Libraries

  • ml4t/data
  • ml4t/engineer
  • ml4t/backtest
  • ml4t/specs
  • ml4t/live
  • ml4t/diagnostic
  • ml4t/models

Required evidence

  • Python 3.12 through 3.14 on Linux, macOS, and Windows
  • Python 3.15 prerelease installation and non-hardware-dependent tests on all three systems
  • Installation from built wheel and public import
  • Tests, Ruff, ty, and package build
  • Stable source and published metadata
  • Strict MkDocs build and correct deployment route
  • Standard issue forms, labels, pull-request linkage, and private vulnerability reporting
  • Central qualification in pull requests and release workflows
  • Current user issue and pull-request response review

Completion

Every linked library issue is closed by a verified pull request and required patch release, or records an exact product-decision or credential blocker with all independent work complete.

Metadata

Metadata

Assignees

No one assigned

    Labels

    compatibility: affectedHas Python, platform, dependency, or cross-library compatibility impactecosystemTracked by a shared ML4T ecosystem requirementpriority: highMaterial user impact requiring prompt remediationstatus: blockedCannot progress until the documented dependency resolvestype: maintenanceInternal maintenance without user-visible behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions