Add TASKS.md: Implementation roadmap for version qualifier support

[Copilot]

Overview

Breaks down the version qualifier specification (docs/qualifier-spec.md) into 14 actionable implementation tasks organized across 6 phases. Provides roadmap for implementing issues #5 and #38.

Release Notes

• Added TASKS.md with detailed implementation breakdown for version qualifier support

Related

Closes #38

---

Task Structure

14 tasks across 6 phases:

1. Core Version Model (2 tasks) - Extend Version class for qualifier parsing and validation
2. Comparison Logic (2 tasks) - Implement precedence rules: SNAPSHOT < ALPHA < BETA < RC < RELEASE < bare < HF
3. Validation Logic (2 tasks) - Update NewVersionValidator for qualifier progression
4. Testing (3 tasks) - Unit tests, integration tests, code quality (≥80% coverage, Pylint ≥9.5)
5. Documentation (3 tasks) - Update README, add examples, update DEVELOPER.md
6. Integration (2 tasks) - Update action.yml and workflows

Each task specifies:

• Priority, effort estimate, spec section references
• Requirements, acceptance criteria, testing approach

Key qualifier rules documented:

• Six allowed patterns: SNAPSHOT, ALPHA, BETA, RC[1-99], RELEASE, HF[1-99]
• Case-sensitive, uppercase only
• Hotfixes come after bare version: v1.0.0 < v1.0.0-HF1 < v1.0.0-HF2
• Numeric comparison for RC/HF suffixes: RC2 < RC10 (not string comparison)

Non-goals explicitly listed:

• Combined qualifiers (RC1-SNAPSHOT)
• Build metadata (RC1+build.123)
• Custom qualifiers beyond the six defined

Implementation order recommended: Model → Comparison → Validation → Testing → Docs → Integration

Follows DEVELOPER.md pattern (line 249) of using SPEC.md/TASKS.md for non-trivial features.

Original prompt

Create a detailed tasks from Spec in docs/qualifier-spec.md

Custom agent used: senior-dev-agent
Agent specialising in pull requests and design trade-offs

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Wed Dec 17 2025 to showcase some of the refinements we've made.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR adds a comprehensive implementation roadmap (TASKS.md) that breaks down the version qualifier specification from docs/qualifier-spec.md into 14 actionable tasks across 6 phases. The document provides a structured approach to implementing version qualifier support (issues #5 and #38), detailing requirements, acceptance criteria, and testing approaches for each task.

Key changes:

• Documents implementation phases from core model enhancement through GitHub Actions integration
• Specifies qualifier rules (SNAPSHOT, ALPHA, BETA, RC[1-99], RELEASE, HF[1-99]) with precedence ordering
• Provides detailed task breakdown with effort estimates and dependencies

[miroslavpojer]

@copilot do double check review using pm-agent

[Copilot]

@copilot do double check review using pm-agent

Double-check review completed. All previous review comments have been properly addressed:

✅ RC/HF patterns exclude 0: RC([1-9][0-9]?) and HF([1-9][0-9]?)
✅ Acceptance criteria explicitly reject RC0, HF0
✅ Permissive parsing pattern documented with note
✅ Coverage target clarified to "Maintain overall project coverage at ≥80%"

Document verified against qualifier-spec.md:

• All 9 spec sections covered
• 14 tasks across 6 phases with clear requirements and acceptance criteria
• Version examples consistently formatted
• Precedence rules accurate (including special HF handling: v1.0.0 < v1.0.0-HF1)
• Non-goals and future options properly documented

No issues found. Document is ready for implementation.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

Line 100 uses inconsistent comparison notation (<) compared to line 102 which shows no qualifier as '(highest for that numeric base)'. Consider using consistent descriptive text like 'RC1 to RC99 (in numeric order)' to match the style of line 102 and avoid confusion with code operators.

Suggested change

	4. `RC1` < `RC2` < ... < `RC99`
	4. `RC1` to `RC99` (in numeric order)

[Copilot]

The implementation order section duplicates information already present in the phase structure. Consider adding value by noting specific inter-task dependencies (e.g., 'Task 2.1 requires Task 1.2 completion') or removing this section to avoid redundancy with the already-sequential phase organization.

Suggested change

	## Implementation Order
	**Recommended sequence:**
	1. **Phase 1:** Core Version Model (Tasks 1.1, 1.2)
	- Foundation for all other work
	- Can be tested independently
	2. **Phase 2:** Comparison Logic (Tasks 2.1, 2.2)
	- Builds on Phase 1
	- Required for validation logic
	3. **Phase 3:** Validation Logic (Tasks 3.1, 3.2)
	- Integrates Phases 1 and 2
	- Core business logic
	4. **Phase 4:** Testing (Tasks 4.1, 4.2, 4.3)
	- Continuous throughout development
	- Final comprehensive pass after Phase 3
	5. **Phase 5:** Documentation (Tasks 5.1, 5.2, 5.3)
	- After implementation is complete
	- Reflects actual implementation
	6. **Phase 6:** Integration (Tasks 6.1, 6.2)
	- Final cleanup and polish
	- After documentation is done