|
1 | 1 | # TODO Items |
2 | 2 |
|
| 3 | +- Suppress PyPy 3.11 with Rust extension until Maturin supports it. |
| 4 | +- Suppress Python 3.13 and 3.14 with Rust extension until Maturin supports it. |
| 5 | + |
3 | 6 | ## Future Enhancements |
4 | 7 |
|
5 | 8 | ### Documentation URL Support for docs-* Tags |
|
17 | 20 |
|
18 | 21 | **Priority:** Future enhancement - current `/stable/` approach is functional for immediate needs. |
19 | 22 |
|
20 | | -## Post-1.29 Development Ideas |
21 | | - |
22 | | -### High Priority |
23 | | - |
24 | | -#### Create tests/README.rst |
25 | | -**Goal:** Document testing conventions and architecture for contributors. |
26 | | -**Details:** Create comprehensive README consistent with write-tests command and documentation/common/tests.rst guidance. Include coverage expectations, test organization, and examples. |
27 | | -**Why:** Complements our new write-tests command and improves developer experience. |
28 | | - |
29 | | -#### Add Github Release Poller to Release Workflow |
| 23 | +### Add Github Release Poller to Release Workflow |
30 | 24 | **Goal:** Improve release workflow reliability by ensuring Github release is registered before artifact publication. |
31 | 25 | **Details:** Add polling step to wait for Github API to register new release before attempting to publish artifacts. Current workflow occasionally fails due to API delays. |
32 | 26 | **Why:** Solves real production reliability issue we've experienced. |
33 | 27 |
|
34 | | -### Medium Priority |
35 | | - |
36 | | -#### Improve Test Coverage |
| 28 | +### Improve Test Coverage |
37 | 29 | **Goal:** Increase test coverage while avoiding integration test hazards. |
38 | 30 | **Details:** Carefully add tests for uncovered code paths, being mindful of integration tests that might clobber production state. Focus on unit tests and safe integration scenarios. |
39 | 31 | **Challenges:** Need to identify safe vs. risky integration test scenarios. |
40 | 32 |
|
41 | | -#### Add MCP Server Support to Claude GitHub Workflow |
| 33 | +### Add MCP Server Support to Claude GitHub Workflow |
42 | 34 | **Goal:** Enhance automated code analysis and testing capabilities. |
43 | | -**Details:** Add useful MCP servers (text-editor, ruff, pyright, context7) to the claude GitHub workflow to improve code quality and analysis automation. |
| 35 | +**Details:** Add useful MCP servers (text-editor, pyright, context7) to the claude GitHub workflow to improve code quality and analysis automation. |
44 | 36 | **Why:** Could significantly improve automated testing and code analysis capabilities. |
45 | 37 |
|
46 | | -### Lower Priority |
47 | | - |
48 | | -#### Enhance Write-Tests Command |
49 | | -**Goal:** Improve write-tests command based on usage experience. |
50 | | -**Details:** Add features like coverage gap analysis, test template generation, or integration with specific testing frameworks based on real usage patterns. |
51 | | - |
52 | | -#### Add More Custom Slash Commands |
53 | | -**Goal:** Expand Claude Code integration with project-specific workflows. |
54 | | -**Ideas:** |
55 | | -- `/analyze-coverage` - Deep dive into coverage gaps |
56 | | -- `/update-template` - Streamlined copier template updates |
57 | | -- `/validate-release` - Pre-release validation checklist |
58 | | - |
59 | | -#### Claude Code Architectural Agents |
60 | | -**Goal:** Create specialized Claude Code agents for architectural work and Python design. |
61 | | -**Ideas:** |
62 | | -- `architect` - For making architectural decisions, creating ADRs, reviewing system design |
63 | | -- `python-designer` - For Python-specific design decisions, API design, module structure |
64 | | -- `requirements-analyst` - For PRD creation, requirements gathering, user story development |
65 | | -- Integration with the new architecture documentation framework |
66 | | - |
67 | | -#### Project Structure Documentation |
68 | | -**Goal:** Add template/documentation/architecture/structure.rst with starter outline. |
69 | | -**Details:** Document the standard project structure pattern generated from our template to help new contributors understand the architectural conventions. |
70 | | -**Why:** Provides immediate context for the consistent patterns across template-generated projects. |
71 | | - |
72 | | -#### Documentation Improvements |
73 | | -**Goal:** Enhance project documentation and developer experience. |
74 | | -**Ideas:** |
75 | | -- API documentation improvements |
76 | | -- Tutorial content for template usage |
77 | | - |
78 | | -#### Release Workflow Enhancements |
| 38 | +### Release Workflow Enhancements |
79 | 39 | **Goal:** Further improve release automation and reliability. |
80 | 40 | **Ideas:** |
81 | 41 | - Automated release notes generation improvements |
82 | 42 | - Multi-stage release validation |
83 | 43 | - Rollback procedures documentation |
84 | | -- Release metrics and monitoring |
| 44 | +- Release metrics and monitoring |
0 commit comments