Milestone 0.2.0
Target: first formal contributor release after establishing the release process.
GitHub milestone: 0.2.0 (create via Create release milestone workflow if it does not exist yet).
Theme
Ship contributor-ready infrastructure, documentation improvements landing on dev, and small bug fixes โ without large experimental RL/evolution features.
In scope
Release infrastructure
| Item | Type | Notes |
|---|---|---|
| #954 | PR | Formal release process, unified versioning, release workflow |
docs/RELEASE.md |
Docs | Maintainer release checklist |
0.2.0 GitHub milestone |
Process | This milestone |
Documentation
| Item | Type | Notes |
|---|---|---|
| #950 | PR | Phase 1 docs reorganization (merged) |
| #952 | PR | Phase 3 content consolidation + link checking |
| #953 | PR | Phase 4 legacy URL redirects + external link CI |
Bug fixes
| Item | Type | Notes |
|---|---|---|
| #944 | PR | Missing FineTuningConfig / EnvFactory imports |
| #930 | Issue | Tracks the import bug above |
Out of scope (defer to later milestones)
Research and experiment follow-ups should not block 0.2.0:
- Inherited-payload ladder (#904)
- Intrinsic goals experiment follow-ups (#892โ#895)
- Baldwinian vs Lamarckian A/B (#849)
- Batch DQN inference (#917)
Release criteria
Before cutting v0.2.0:
- All In scope PRs merged to
dev devCI green (tests, deterministic-simulation)CHANGELOG.mdhas a## [0.2.0]sectionfarm/_version.pybumped to0.2.0- Release PR merged to
mainand GitHub Release published
Changelog draft (fill on release)
## [0.2.0] - YYYY-MM-DD
### Added
- Formal release process and unified package versioning
### Changed
- Documentation site reorganization and link-check CI
### Fixed
- Missing imports for FineTuningConfig and EnvFactory