Development

This section defines how ETLantic is designed, tested, contributed to, and released.

Contributor essentials

• Contributing
• Coding Standards
• Testing
• Documentation
• Release Process
• Support policy
• Governance
• Code of Conduct
• API stability and deprecation
• Maintained 0.21 Documentation Audit
• Maintained 0.20 Documentation Audit
• Maintained 0.18 Documentation Audit
• Historical 0.17 Documentation Audit
• Migration 0.20 → 0.21
• Exit gate 0.21
• Migration 0.19 → 0.20
• Exit gate 0.20
• Migration 0.17 → 0.18
• Migration 0.16 → 0.17
• Migration 0.15 → 0.16
• Migration 0.4 → 0.5
• Migration 0.5 → 0.6
• Migration 0.6 → 0.7
• Migration 0.7 → 0.8
• Migration 0.8 → 0.9
• Migration 0.9 → 0.10
• Migration 0.10 → 0.11
• Migration 0.11 → 0.12
• Migration 0.12 → 0.13
• Migration 0.13 → 0.14
• Migration 0.14 → 0.15
• Roadmap summary
• Full roadmap
• Dependency Strategy

Decisions

• Design Decisions
• Architecture Decisions
• Benchmarks
• Performance guidance
• Performance baselines

Maintainer plans and records (internal)

These pages sequence future work. They are not product user guides:

• 0.18 Gate A — Versioned Tabular Interchange (shipped record)
• FastAPI Integration Plan
• Schema Drift and Evolution Plan
• ETL Reliability and Recovery Plan
• TransformationModel Incubation Plan
• SQLModel Integration Plan
• SparkForge Feature Adoption
• Portable Transformation Implementation Plan
• Local Scheduler and Prefect Integration Plan
• DTCS and Portable Transformation Evolution
• DTCS 2.0 Portable Relational Publication Record
• DTCS 3.0 Rich Portable Analytics Publication Record

Start with the roadmap for sequencing and the decision records for architectural boundaries.

The Documentation Status chapter defines how design examples, proposals, and normative requirements should be interpreted during implementation.