plan: create release-management-optimization roadmap topic
Created comprehensive staged workplan for enhancing release management infrastructure with robust validation using the schema system. **Critical Issues Identified**: - setuptools-scm missing tag_regex configuration - markitect --version returns 'unknown' instead of actual version - CHANGELOG shows v0.9.0 (2025-11-14) but git tag never created - No validation for CHANGELOG format or version-tag consistency **Solution Approach**: Create changelog-schema-v1.0.md to validate Keep a Changelog format, demonstrating schema evolution in real-world use case. **Staged Workplan**: - Stage 1 (45 min): Critical fixes to unblock v0.10.0 release - Stage 2 (2.5 hrs): CHANGELOG schema creation and validation - Stage 3 (2 hrs): Release capability enhancements - Stage 4 (optional): Schema system extensions **Showcase Feature**: 'The release that validates itself' - v0.10.0 uses its own schema system to validate its CHANGELOG - Perfect demonstration of schema evolution practical value **Next Version**: v0.10.0 (not v0.9.0) - CHANGELOG already shows v0.9.0 as released - Must maintain version history integrity
This commit is contained in:
39
roadmap/260106-release-management-optimization/README.md
Normal file
39
roadmap/260106-release-management-optimization/README.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# Release Management Optimization
|
||||
|
||||
**Created**: 2026-01-06
|
||||
**Status**: Planning → Ready to implement
|
||||
**Priority**: High (blocks v0.10.0 release)
|
||||
|
||||
## Quick Summary
|
||||
|
||||
Enhance release management with robust validation using the schema system we just built. Creates a perfect showcase: **validate CHANGELOG.md with a changelog schema**.
|
||||
|
||||
## Critical Issues Found
|
||||
|
||||
1. **setuptools-scm bug**: Missing tag_regex → `markitect --version` returns "unknown"
|
||||
2. **Missing v0.9.0 tag**: CHANGELOG says v0.9.0 released but git tag never created
|
||||
3. **No validation**: No checks for CHANGELOG format or version-tag consistency
|
||||
|
||||
## Solution
|
||||
|
||||
Create **changelog-schema-v1.0.md** to validate Keep a Changelog format, integrate into release workflow. Demonstrates schema evolution in action!
|
||||
|
||||
## Staged Approach
|
||||
|
||||
- **Stage 1** (45 min): Critical fixes → unblock v0.10.0 release
|
||||
- **Stage 2** (2.5 hrs): CHANGELOG schema → showcase feature
|
||||
- **Stage 3** (2 hrs): Release tooling enhancements
|
||||
- **Stage 4** (optional): Schema extensions (hooks/agents)
|
||||
|
||||
**Recommended**: Standard Track (Stages 1-3) = 5 hours for production-ready release management
|
||||
|
||||
## Files
|
||||
|
||||
- `WORKPLAN.md` - Detailed staged implementation plan
|
||||
- `DONE.md` - Completion checklist (when finished)
|
||||
|
||||
## Philosophy
|
||||
|
||||
> "Use the tools we build to improve the tools we build."
|
||||
|
||||
Release v0.10.0 becomes: **The release that validates itself** 🎯
|
||||
Reference in New Issue
Block a user