-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
retrospectiveSprint retrospective issueSprint retrospective issue
Description
What went well?
- Sprint Goal met 100%: all 6 issues closed, 0 carried over
- Release Drafter + APK packaging job worked smoothly out of the box — nfpm handles Alpine with no extra config
- Fixing the release-drafter workflow (removing
pull_requesttrigger) unblocked the draft generation that had been silently broken - TDD discipline: tests (test: add integration tests for --delimiter, --tsv, and --header flags #73) were written as a dedicated issue before merging the feature (JSON output format (--json) #44 was already done, but the test gap was tracked and closed)
- Docs gap identified proactively and tracked as issue Update docs for --json flag and Alpine APK install #76 before Sprint Review
What could be improved?
- Release Drafter miscategorized APK (feat: add APK package for Alpine Linux to release workflow #75) as Maintenance instead of Feature —
feat:prefix on a CI/packaging PR is ambiguous; consider usingchore:for pure workflow changes andfeat:only for user-facing features - Issue Auto-remove status labels on issue close #43 (auto-remove status labels) retained a stale
status:readylabel after closing — the very automation it implemented wasn't applied to itself - PR feat: add --json output flag #74 (--json) appeared twice in the auto-generated release notes — investigate release-drafter category rules to prevent double-listing
Action items for next sprint
- Review release-drafter category rules to avoid duplicate entries and miscategorization
- Consider tightening commit prefix conventions:
feat:= user-facing only,chore:= CI/tooling/packaging
Metrics
- Planned: 6 issues
- Completed: 6 issues (100%)
- Carried over: 0
- Sprint Goal met: Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
retrospectiveSprint retrospective issueSprint retrospective issue